Thread View: gnu.gcc.bug
1 messages
1 total messages
Started by joris
Thu, 15 Oct 1992 13:12
bug in -pipe flag
Author: joris
Date: Thu, 15 Oct 1992 13:12
Date: Thu, 15 Oct 1992 13:12
41 lines
1646 bytes
1646 bytes
Dear reader, I have built gcc 2.2.2 for iris4d-irix4, following the installation guide. No file is modified, (the stage2 and stage3 binaries compare equal). Trying the -pipe option results in: hera % cat >file.c /* nothing */ hera % gcc -c -pipe file.c gcc: -pipe is not supported. as: Error: no source, object or ucode file specified file.c:2: output pipe has been closed Segmentation fault (core dumped) and dbx said: hera % dbx `which gcc` dbx version 2.10 11/15/91 2:02 Type 'help' for help. Reading symbolic information of `./gcc' . . . Process name from core dump: gcc Process died at pc 0x4089b0 of signal : Segmentation fault [using memory image in core] (dbx) where > 0 .strcmp.strcmp(0x0, 0x100048a4, 0x10015bc0, 0xa, 0xc, 0x2) ["sys/close.s":16, 0x4089ac] 1 execute() ["gcc.c":1541, 0x40198c] (dbx) The 'specs' file for mips-irix tells correctly that the mips assembler does not support pipes. For some reason (I don't have the time to investigate the 'specs' logic) gcc does set up the full pipeline cpp | cc1 | as, and later dumps core at "gcc.c":1541. Suggestion: gcc -pipe file.c does cpp file.c | cc1 > tmpfile ; as tmpfile -o file.o Joris vdr Geer joris@rijnh.nl
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads