------- Comment #2 from acahalan at gmail dot com 2006-09-26 04:31 -------
(In reply to comment #1)
> A quick question here. Why not use a .s file instead?
REASON #1
Sometimes people want to use --combine -fwhole-program, but the documentation
for -fwhole-program starts with this:
"Assume that the current compilation unit represents whole program being
compiled."
It is also implied, and stated elsewhere, that this only works for C. Thus it
is apparently not allowed to have assembly, C++, Objective-C, Objective-C++, or
weirder stuff.
REASON #2
Using a .s file does not allow the naked function to have static scope.
REASON #3
Even when it will work OK, the separate file is simply annoying. People
naturally want to group functions together without being needlessly restricted.
--
acahalan at gmail dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |acahalan at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25967
