public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "howarth at nitro dot med.uc.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/46510] r166812 breaks bootstrap on x86_64-apple-darwin10
Date: Tue, 16 Nov 2010 23:22:00 -0000 [thread overview]
Message-ID: <bug-46510-4-KMBmp3pfFA@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-46510-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46510
--- Comment #2 from Jack Howarth <howarth at nitro dot med.uc.edu> 2010-11-16 23:07:53 UTC ---
Created attachment 22425
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=22425
preprocessed source for libgomp/barrier.c
Created with...
/sw/src/fink.build/gcc46-4.6.0-1000/darwin_objdir/./gcc/xgcc
-B/sw/src/fink.build/gcc46-4.6.0-1000/darwin_objdir/./gcc/
-B/sw/lib/gcc4.6/x86_64-apple-darwin10.5.0/bin/
-B/sw/lib/gcc4.6/x86_64-apple-darwin10.5.0/lib/ -isystem
/sw/lib/gcc4.6/x86_64-apple-darwin10.5.0/include -isystem
/sw/lib/gcc4.6/x86_64-apple-darwin10.5.0/sys-include -DHAVE_CONFIG_H -I.
-I../../../gcc-4.6-20101116/libgomp
-I../../../gcc-4.6-20101116/libgomp/config/bsd
-I../../../gcc-4.6-20101116/libgomp/config/posix
-I../../../gcc-4.6-20101116/libgomp -Wall -pthread -Werror -g -O2 -MT
barrier.lo -MD -MP -MF .deps/barrier.Tpo -c
../../../gcc-4.6-20101116/libgomp/barrier.c -fno-common -DPIC --save-temps -v
-o .libs/barrier.o
next prev parent reply other threads:[~2010-11-16 23:08 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-16 23:06 [Bug middle-end/46510] New: " howarth at nitro dot med.uc.edu
2010-11-16 23:08 ` [Bug middle-end/46510] " pinskia at gcc dot gnu.org
2010-11-16 23:22 ` howarth at nitro dot med.uc.edu [this message]
2010-11-16 23:42 ` dominiq at lps dot ens.fr
2010-11-16 23:52 ` dominiq at lps dot ens.fr
2010-11-17 11:55 ` [Bug middle-end/46510] [4.6 Regression] " rguenth at gcc dot gnu.org
2010-11-17 16:22 ` hubicka at gcc dot gnu.org
2010-11-17 16:37 ` howarth at nitro dot med.uc.edu
2010-11-17 16:43 ` howarth at nitro dot med.uc.edu
2010-11-17 21:43 ` dominiq at lps dot ens.fr
2010-11-18 10:12 ` rguenth at gcc dot gnu.org
2010-11-18 15:29 ` ramana at gcc dot gnu.org
2010-11-18 15:32 ` ramana at gcc dot gnu.org
2010-11-18 16:10 ` dominiq at lps dot ens.fr
2010-11-18 23:44 ` dave at hiauly1 dot hia.nrc.ca
2010-11-18 23:46 ` dominiq at lps dot ens.fr
2010-11-19 0:08 ` dave at hiauly1 dot hia.nrc.ca
2010-11-19 14:59 ` howarth at nitro dot med.uc.edu
2010-11-21 13:33 ` hubicka at gcc dot gnu.org
2010-11-21 16:17 ` dominiq at lps dot ens.fr
2010-11-21 16:32 ` hubicka at ucw dot cz
2010-11-21 17:25 ` howarth at nitro dot med.uc.edu
2010-11-21 17:27 ` howarth at nitro dot med.uc.edu
2010-11-21 17:51 ` hubicka at ucw dot cz
2010-11-21 18:16 ` howarth at nitro dot med.uc.edu
2010-11-21 18:37 ` dominiq at lps dot ens.fr
2010-11-21 18:49 ` dominiq at lps dot ens.fr
2010-11-21 18:55 ` Jan Hubicka
2010-11-21 18:57 ` hubicka at ucw dot cz
2010-11-21 23:06 ` hubicka at gcc dot gnu.org
2010-11-22 0:05 ` howarth at nitro dot med.uc.edu
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-46510-4-KMBmp3pfFA@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: link
Be 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).