51973 – GCC does not compile comments beginning with a hash sign (#) in *.S files

Bug 51973 - GCC does not compile comments beginning with a hash sign (#) in *.S files

Summary: GCC does not compile comments beginning with a hash sign (#) in *.S files

Status:	RESOLVED NEEDINFO

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	[OLD] Unspecified (show other bugs)
Hardware:	x86 Linux

Importance:	High normal (vote)
Assignee:	Please assign to toolchain

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2004-05-25 00:31 UTC by Axel Schmalowsky
Modified:	2005-01-09 13:13 UTC (History)
CC List:	0 users

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Axel Schmalowsky 2004-05-25 00:31:30 UTC

When I emerge something of the media-glx tree, I always get an error message like: "Invalid statement: #Check|OK in file have_mmx.S".
It should apparently be a comment, not a macro; and gcc complains about that.
I changed it into a C-comment, and it worked (but I had to install it "manually").
[ Sorry for that "bad english" ]

Reproducible: Always
Steps to Reproduce:
1.
2.
3.




see Details

Comment 1 Travis Tilley (RETIRED) gentoo-dev

2004-07-15 02:05:49 UTC

what might that something be? does this bug still exist with 3.4.1/3.3.4? can you include the output of emerge info? has this been reported upstream?

Comment 2 Travis Tilley (RETIRED) gentoo-dev

2004-08-18 00:40:04 UTC

needinfo

Comment 3 David Westley 2005-01-09 13:13:26 UTC

I was experiencing this problem with gtk+-2.4.14 and narrowed it down to using -std in my CFLAGS so maybe it would be an idea to put a filter-flags in the ebuild to remove the -std flag for these?