This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On Fri, Jun 18, 2004 at 06:01:10PM -0700, Ziemowit Laski wrote:Since the standard does not define the semantics of the call, we may as well let it through. I believe that is standard-conforming.
You're wrong.
# 6.5.2.2:
# 9 If the function is defined with a type that is not compatible with the
# type (of the expression) pointed to by the expression that denotes the
# called function, the behavior is undefined.
Just what exactly is wrong with the asm() trick I came up with? I am, of course, asking for technical arguments, not aesthetic ones.
Technical argument? How about needless creation of FUNCTION_DECLs.
I'd have thought the aesthetic argument was good enough, however.
Hm... I can't really claim that I never consider aesthetics in my hac^H^H^Hengineering activities, although technical considerations always trump them, as they should. I guess I'll just wait for your METHOD_EXPR work, and then will decide which approach is more disgusting. :-)
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |