This is the mail archive of the libc-hacker@sourceware.cygnus.com mailing list for the glibc project.
Note that libc-hacker is a closed list. You may look at the archives of this list, but subscription and posting are not open.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Andreas Schwab wrote: > > Scott Bambrough <scottb@netwinder.org> writes: > > |> This fix is fine, but I don't believe it should be necessary. The C++ parsing > |> routines should recognize they are in an inline assembler construct and act > |> accordingly. IMHO, this is a compiler bug. > > No, in C++ `::' is a separate token, that is different from `: :'. > I see your point, but the colon also acts as a delimiter between different parts of the inline assembler statement; parts that are there explicitly for the compiler's benefit. I think the compiler should be able to tokenize this statement without regard to whitespace. I'll ask on the gcc list, cause I'm curious what the correct answer is. Scott -- Scott Bambrough - Software Engineer REBEL.COM http://www.rebel.com NetWinder http://www.netwinder.org
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |