public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "klawson at ad-holdings dot co dot uk" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/13920] New: Segmentation Faults with optimization greater than 0 Date: Thu, 29 Jan 2004 12:11:00 -0000 [thread overview] Message-ID: <20040129121048.13920.klawson@ad-holdings.co.uk> (raw) sh-elf-gcc on cygwin fails with segmentation faults when building the eCos FreeBSD stack. The same code can be built using the linux sh-elf-gcc build. sh-elf-gcc -c -I/ecos-c/data/ecos/net1_install/include -I/ecos-c/cygwin/opt/ecos/ecos-2.0/packages/net/bsd_tcpip/v2_0 -I/ecos-c/cygwin/opt/ecos/ecos-2.0/packages/net/bsd_tcpip/v2_0/src -I/ecos-c/cygwin/opt/ecos/ecos-2.0/packages/net/bsd_tcpip/v2_0/tests -I. -I/ecos-c/cygwin/opt/ecos/ecos-2.0/packages/net/bsd_tcpip/v2_0/src/sys/netinet/ -mb -m3 -Wall -Wpointer-arith -Wstrict-prototypes -Winline -Wundef -Woverloaded-virtual -ggdb -O2 -ffunction-sections -fdata-sections -fno-rtti -fno-exceptions -fvtable-gc -finit-priority -D_KERNEL -save-temps -Wp,-MD,src/sys/netinet/tcp_input.tmp -o src/sys/netinet/net_bsd_tcpip_tcp_input.o /ecos-c/cygwin/opt/ecos/ecos-2.0/packages/net/bsd_tcpip/v2_0/src/sys/netinet/tcp_input.c /ecos-c/cygwin/opt/ecos/ecos-2.0/packages/net/bsd_tcpip/v2_0/src/sys/netinet/tcp_input.c: In function `cyg_tcp_input': /ecos-c/cygwin/opt/ecos/ecos-2.0/packages/net/bsd_tcpip/v2_0/src/sys/netinet/tcp_input.c:405: warning: implicit declaration of function `cyg_in_pseudo' make[1]: Leaving directory `/ecos-c/data/ecos/net1_build/net/bsd_tcpip/v2_0' /ecos-c/cygwin/opt/ecos/ecos-2.0/packages/net/bsd_tcpip/v2_0/src/sys/netinet/tcp_input.c: In function `tcp_pulloutofband': make: Leaving directory `/ecos-c/data/ecos/net1_build' /ecos-c/cygwin/opt/ecos/ecos-2.0/packages/net/bsd_tcpip/v2_0/src/sys/netinet/tcp_input.c:2541: internal error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions. make[1]: *** [src/sys/netinet/tcp_input.o.d] Error 1 make: *** [build] Error 2 Segmentation faults can also occur in other areas of this file. Host environment is cygwin 1.5.5. The sh-elf toolchain is that obtainable from eCoscentric, but the same fault also occurs when building your own toolchain. gcc was configured using: configure --target=sh-elf --prefix=/newtools --enable-languages=c,c++ \ --with-gnu-as --with-gnu-ld --with-newlib \ --with-gxx-include-dir=/gnutools/sh-elf/include \ -v 2>&1 | tee configure.out The fault does not occur on a linux build of sh-elf-gcc. -- Summary: Segmentation Faults with optimization greater than 0 Product: gcc Version: 3.2.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: c AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: klawson at ad-holdings dot co dot uk CC: gcc-bugs at gcc dot gnu dot org GCC build triplet: i686-pc-cygwin GCC host triplet: i686-pc-cygwin GCC target triplet: sh-elf http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13920
next reply other threads:[~2004-01-29 12:11 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-01-29 12:11 klawson at ad-holdings dot co dot uk [this message] 2004-01-29 12:12 ` [Bug c/13920] " klawson at ad-holdings dot co dot uk 2004-01-29 12:30 ` klawson at ad-holdings dot co dot uk 2004-01-29 15:48 ` pinskia at gcc dot gnu dot org 2004-02-02 11:46 ` klawson at ad-holdings dot co dot uk 2004-02-02 14:34 ` pinskia at gcc dot gnu dot org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20040129121048.13920.klawson@ad-holdings.co.uk \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).