[Bug inline-asm/29357] inline asm %c0 template form not documented

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29357 Michael Schulze changed: What|Removed |Added CC||mschulze at ivs dot

[Bug target/45263] registers used in __do_global_ctors can get clobbered

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45263 --- Comment #11 from Michael Schulze 2010-12-06 09:07:19 UTC --- (In reply to comment #9) > This is essentially identical to the patch I provided for > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44617 > so it looks good to me. I hadn't see that

[Bug target/46779] wrong code generation for array access

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46779 --- Comment #4 from Michael Schulze 2010-12-03 14:16:30 UTC --- > I don't know anything about AVR, so I can't say that (I just noticed the r1 > issue). Ok due to the compiler abi for the avr, r0,r1 are fixed registers that are never allocated by

[Bug c/46779] wrong code generation for array access

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46779 --- Comment #2 from Michael Schulze 2010-12-03 13:58:40 UTC --- (In reply to comment #1) > at least I see r1 use in the asm but no clobber for it, instead it clobbers > the seemingly unused r31. Yes correct, r1 is not clobbered, however, I tested

[Bug c/46779] New: wrong code generation for array access

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46779 Summary: wrong code generation for array access Product: gcc Version: 4.4.0 Status: UNCONFIRMED Severity: critical Priority: P3 Component: c AssignedTo: unassig...@gc

[Bug target/45263] registers used in __do_global_ctors can get clobbered

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45263 --- Comment #8 from Michael Schulze 2010-11-30 15:21:57 UTC --- Comment on attachment 22579 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=22579 alternative patch using register r15 instead of r20 avoids pushing/poping >diff -Naur gcc-4.5.1

[Bug target/45263] registers used in __do_global_ctors can get clobbered

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45263 --- Comment #7 from Michael Schulze 2010-11-30 15:16:20 UTC --- Created attachment 22579 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=22579 alternative patch using register r15 instead of r20 avoids pushing/poping In reaction to bug 29141

[Bug c++/46706] New: global constructors does not work properly since changes from bug 29141

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46706 Summary: global constructors does not work properly since changes from bug 29141 Product: gcc Version: 4.4.0 Status: UNCONFIRMED Severity: critical Priority: P3

[Bug target/29141] static constructors beyond 64k fail

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29141 Michael Schulze changed: What|Removed |Added CC||mschulze at ivs dot

[Bug c++/45964] The compiler does not complain about a required template keyword.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45964 --- Comment #14 from Michael Schulze 2010-10-12 07:08:16 UTC --- (In reply to comment #13) > (In reply to comment #12) > > Should I write two bug reports about the found problems? > > Sure. Bug #45975 and Bug #45976 describe both problems.

[Bug c++/45976] New: optional template keyword is not accepted by g++

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45976 Summary: optional template keyword is not accepted by g++ Product: gcc Version: 4.5.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ AssignedTo: una

[Bug c++/45975] New: template keyword is not allowed, however, accepted by g++

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45975 Summary: template keyword is not allowed, however, accepted by g++ Product: gcc Version: 4.5.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component

[Bug c++/45964] The compiler does not complain about a required template keyword.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45964 --- Comment #12 from Michael Schulze 2010-10-11 17:37:30 UTC --- Should I write two bug reports about the found problems?

[Bug c++/45964] The compiler does not complain about a required template keyword.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45964 --- Comment #8 from Michael Schulze 2010-10-11 14:03:46 UTC --- Ok. If I understand the standard correct is the template keyword on the following places const int A::template B::value = A::template B::C::value; correct but optional, right? The

[Bug c++/45964] The compiler does not complain about a required template keyword.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45964 Michael Schulze changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|INVALID

[Bug c++/45964] The compiler does not complain about a required template keyword.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45964 Michael Schulze changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|INVALID

[Bug c++/45964] The compiler does not complain about a required template keyword.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45964 --- Comment #2 from Michael Schulze 2010-10-11 11:27:14 UTC --- (In reply to comment #1) > (In reply to comment #0) > > template > > template > > const int A< a>::B::template value = A::B::C::value; > > Are you s

[Bug c++/45964] New: The compiler does not complain about a required template keyword.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45964 Summary: The compiler does not complain about a required template keyword. Product: gcc Version: 4.4.0 Status: UNCONFIRMED Severity: normal Priority: P3 C