🚀 go-pugleaf

[I mailed this to bug-gcc@prep.ai.mit.edu a week ago, but never
 saw it appear on the gnu.gcc.bug newsgroup]

GCC 1.40 on DECstations doesn't handle generated C files correctly
(it doesn't do the right thing with #line's), and debuggers get
confused, looking at the generated C code, instead of the original
source.  GCC 1.40 running on Sparcstations, on the other hand,
works correctly.

The problem is that the .file directive at the beginning of the
asm file emitted by GCC points to the generated C file instead
of the original file specifed in a #line directive.

For example, given /tmp/foo.c, which looks like
	#line 1 "/u/gvr/foo.c"
	/* code */
the first line of foo.s will be
	.file "/tmp/foo.c"
As /tmp/foo.c is generated on the fly and removed after compilation,
this is a problem for debugging.

The following extract from compile_file() in toplev.c indicates that
GCC is trying to do the right thing, but failing:
  /* the beginning of the file is a new line; check for # */
  /* With luck, we discover the real source file's name from that
     and put it in input_filename.  */
  ungetc (check_newline (), finput);

GCC 1.40 on Sparcstations doesn't issue an initial directive corresponding
to .file, so it doesn't screw up.
________________
George V. Reilly `At the end of my #line' gvr@cs.brown.edu  +1 (401) 863-7693
uunet!brunix!gvr   gvr@browncs.bitnet	  Box 1910, Brown U, Prov, RI 02912