[Bug c/25175] Meaningless pre-processor lineno comments inserted

2005-11-29 Thread jw203198 at hotmail dot com
--- Comment #10 from jw203198 at hotmail dot com 2005-11-30 04:16 --- > > If you use -E -H -g -fno-working-directory, you will not see the directory > name. Thanks, I can use that. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25175

[Bug c/25175] Meaningless pre-processor lineno comments inserted

2005-11-29 Thread jw203198 at hotmail dot com
--- Comment #8 from jw203198 at hotmail dot com 2005-11-30 03:52 --- (In reply to comment #7) > (In reply to comment #6) > > > Your orginal example does not show a difference for -H at all. > Wait a minute, -E outputs the preprocessed source. -H outputs the files which

[Bug c/25175] Meaningless pre-processor lineno comments inserted

2005-11-29 Thread jw203198 at hotmail dot com
--- Comment #6 from jw203198 at hotmail dot com 2005-11-30 03:37 --- > Your orginal example does not show a difference for -H at all. Does for me: pc:~/work/stats $ cc -E -H x.c # 1 "x.c" # 1 "" # 1 "" # 1 "x.c" mai

[Bug c/25175] Meaningless pre-processor lineno comments inserted

2005-11-29 Thread jw203198 at hotmail dot com
--- Comment #4 from jw203198 at hotmail dot com 2005-11-30 02:55 --- > Can you show where -H will give you the CWD? Use my original example and add -H. I *never* had "-save-temps" in my example so I don't understand why you are corrupting my example so. And I *nev

[Bug c/25173] gcc outputs unnecessary warnings

2005-11-29 Thread jw203198 at hotmail dot com
--- Comment #4 from jw203198 at hotmail dot com 2005-11-30 02:52 --- Don't you think that forcing people to cast pointers is much much more dangerous than allowing simple equivalence of pointers when they aren't even being derefenced? What about this: struct x *f() {

[Bug c/25175] Meaningless pre-processor lineno comments inserted

2005-11-29 Thread jw203198 at hotmail dot com
--- Comment #2 from jw203198 at hotmail dot com 2005-11-30 02:18 --- (In reply to comment #1) > The current directory is outputted so that when compiling with -save-temps -g > is no different from -g. The double // is not really a problem at all. > That is rather unfortunate

[Bug c/25175] New: Meaningless pre-processor lineno comments inserted

2005-11-29 Thread jw203198 at hotmail dot com
g ReportedBy: jw203198 at hotmail dot com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25175

[Bug c/25173] gcc outputs unnecessary warnings

2005-11-29 Thread jw203198 at hotmail dot com
--- Comment #2 from jw203198 at hotmail dot com 2005-11-30 02:07 --- But surely that example isn't evidence of a problem. Because if somebody codes: int *p = f(); does it really matter what the signedness of f()'s return value is? The caller has a pointer whi

[Bug c/25173] New: gcc outputs unnecessary warnings

2005-11-29 Thread jw203198 at hotmail dot com
Version: 4.0.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jw203198 at hotmail dot com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25173

[Bug c/25170] New: Erroneous error message for simple macro

2005-11-29 Thread jw203198 at hotmail dot com
imple macro Product: gcc Version: 4.0.1 Status: UNCONFIRMED Severity: major Priority: P3 Component: c AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jw203198 at hotmail dot com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25170

[Bug c/25129] New: asm volatile optimizes to invalid operands

2005-11-27 Thread jw203198 at hotmail dot com
accs) ); } -- Summary: asm volatile optimizes to invalid operands Product: gcc Version: 4.0.1 Status: UNCONFIRMED Severity: major Priority: P3 Component: c AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: