http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60906
--- Comment #8 from Harald van Dijk ---
Oh, based on the existing error for
void f();
void f() __attribute__((regparm(3)));
which is accepted on x86-64, but fails on x86-32 with
test.cc:2:36: error: new declaration ‘void f()’
void f() __attrib
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60906
--- Comment #7 from Sriraman Tallam ---
(In reply to Jakub Jelinek from comment #6)
> GCC has like 60 or 70 target independent attributes plus sometimes various
> target dependent attributes. Figuring out which are ABI changing and must
> be erro
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60906
--- Comment #6 from Jakub Jelinek ---
GCC has like 60 or 70 target independent attributes plus sometimes various
target dependent attributes. Figuring out which are ABI changing and must be
errored out on mismatch, which are safe to ignore, which
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60906
--- Comment #5 from Harald van Dijk ---
(In reply to Sriraman Tallam from comment #4)
> I do not understand why the default function's attributes should be applied
> to all declarations?
The alternative is to not apply them to all declarations, b
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60906
Sriraman Tallam changed:
What|Removed |Added
CC||tmsriram at google dot com
--- Comment
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60906
--- Comment #3 from Harald van Dijk ---
Speaking only as a user, the behaviour I personally naïvely expected would be
to push the default function's attributes into each target-specific function's
attributes, and use the already existing rules for
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60906
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org,
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60906
Richard Biener changed:
What|Removed |Added
Keywords||wrong-code
Target|
