public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rask at sygehus dot dk" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/27266] New: syncronization primitives cause ICE with -march=pentium or better Date: Sun, 23 Apr 2006 09:55:00 -0000 [thread overview] Message-ID: <bug-27266-12574@http.gcc.gnu.org/bugzilla/> (raw) Mainline is ICE'ing on testsuite/gcc.c-torture/compile/sync-1.c for some arguments to -march. For example: ./xgcc -B. -O2 /mnt/sysfs/rask/cvssrc/gcc/gcc/testsuite/gcc.c-torture/compile/sync-1.c -S -o /tmp/sync-1.s -march=pentium /mnt/sysfs/rask/cvssrc/gcc/gcc/testsuite/gcc.c-torture/compile/sync-1.c: In function 'test_lock': /mnt/sysfs/rask/cvssrc/gcc/gcc/testsuite/gcc.c-torture/compile/sync-1.c:261: internal compiler error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://gcc.gnu.org/bugs.html> for instructions. It works with: i386, i486, winchip-c6, winchip2 and c3. It fails with: pentium, pentium-mmx, pentiumpro, pentium2, pentium3, pentium4, nocona, prescott, k6, k6-2, k6-3, k8, athlon, opteron and c3-2. The gcc-4.1.0-3 compiler shipped by Red Hat fails in the same way for the same arguments to -march. -- Summary: syncronization primitives cause ICE with -march=pentium or better Product: gcc Version: 4.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: rask at sygehus dot dk GCC build triplet: i686-pc-linux-gnu GCC host triplet: i686-pc-linux-gnu GCC target triplet: i686-pc-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27266
next reply other threads:[~2006-04-23 9:55 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-04-23 9:55 rask at sygehus dot dk [this message] 2006-04-23 14:46 ` [Bug c/27266] " rask at sygehus dot dk 2006-04-23 16:09 ` [Bug target/27266] [4.2 Regression] " pinskia at gcc dot gnu dot org 2006-04-23 16:10 ` pinskia at gcc dot gnu dot org 2006-05-08 7:51 ` pinskia at gcc dot gnu dot org 2006-05-09 23:57 ` janis at gcc dot gnu dot org 2006-05-20 8:01 ` kazu at gcc dot gnu dot org 2006-05-20 8:43 ` kazu at gcc dot gnu dot org 2006-05-20 19:41 ` kazu at gcc dot gnu dot org 2006-05-22 17:38 ` rth at gcc dot gnu dot org 2006-05-22 17:56 ` kazu at gcc dot gnu dot org 2006-05-22 17:56 ` kazu 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=bug-27266-12574@http.gcc.gnu.org/bugzilla/ \ --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).