This is the mail archive of the 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]

Re: Why does casting a function generate a run-time abort? (Ziemowit Laski)  wrote on 18.06.04 in <>:

> trick I came up with?  I am, of course, asking for technical
> arguments, not aesthetic ones.

That's a false dichotomy. Most aesthetic arguments in programming *are*  

Personally, I tend to think that aesthetical technical arguments should  
nearly always trump non-aesthetical technical arguments. Doing it the  
other way around gets you ugly, unmaintainable code. Like those thousands- 
of-lines routines in gcc that nobody wants to touch.

In this specific case, I think the real question is "do the GIMPLE-based  
optimizers need to know anything about how Objective C method calls work?"  
- and it seems to me the answer is NO - there's nothing there to optimize  
at that level. (Is there? Could you, for example, look up a method once  
and call it often? In which case it would make sense to have both a  
LOOKUPMETHOD and a CALLMETHOD. Note that that's a common manual  
optimization in GNUstep ...)

RTL, of course, *does* need to know.

MfG Kai

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]