[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 ian at airs dot com
--- Comment #9 from ian at airs dot com 2005-11-30 04:06 --- This is documented behaviour. The -g option enables the -fworking-directory option, as described in the documentation of -fworking-directory. It is the -fworking-directory option which is printing the directory name. If you

[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 > are included.

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

2005-11-29 Thread pinskia at gcc dot gnu dot org
--- Comment #7 from pinskia at gcc dot gnu dot org 2005-11-30 03:42 --- (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 are included. Again this is not a bug. -

[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" main(){} and: pc:~/work/stats $ cc -E -H -g

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

2005-11-29 Thread pinskia at gcc dot gnu dot org
--- Comment #5 from pinskia at gcc dot gnu dot org 2005-11-30 03:06 --- (In reply to comment #4) > > Can you show where -H will give you the CWD? > Use my original example and add -H. Your orginal example does not show a difference for -H at all. pc64:~> gcc -H t.c -g pc64:~> gcc -H t.c

[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 *never* used a -S flag ei

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

2005-11-29 Thread pinskia at gcc dot gnu dot org
--- Comment #3 from pinskia at gcc dot gnu dot org 2005-11-30 02:24 --- (In reply to comment #2) > That is rather unfortunate. > Because if you use the -H option then you will get different output depending > on whether you use "-g" or not. So while you might be helping the > "-save-tem

[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. Because

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

2005-11-29 Thread pinskia at gcc dot gnu dot org
--- Comment #1 from pinskia at gcc dot gnu dot org 2005-11-30 02:14 --- 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. -- pinskia at gcc dot gnu dot org changed: What