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 target/54404] [4.8 Regression] *cfstring* failures for (obj-c|g)++ on *-apple-darwin* after revision 186978
Date: Wed, 17 Oct 2012 23:58:00 -0000 [thread overview]
Message-ID: <bug-54404-4-o0L4OkYP80@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54404-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54404
--- Comment #10 from Jack Howarth <howarth at nitro dot med.uc.edu> 2012-10-17 23:58:36 UTC ---
(In reply to comment #9)
> Note the the string1.m/string1.mm failures are from warnings and the resulting
> binaries run fine.
These linker warnings are http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48094. I
also see these failures under darwin10 with Xcode 4.2's linker. This linker
warning doesn't occur with the linker from Xcode 3.2.6 under darwin10.
next prev parent reply other threads:[~2012-10-17 23:58 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-29 10:33 [Bug target/54404] New: [4.8 Regression] *cfstring* failures for (obj-c|g)++ on *-apple-darwin* after revision 186789 dominiq at lps dot ens.fr
2012-10-13 19:27 ` [Bug target/54404] " howarth at nitro dot med.uc.edu
2012-10-14 5:52 ` dominiq at lps dot ens.fr
2012-10-14 19:26 ` [Bug target/54404] [4.8 Regression] *cfstring* failures for (obj-c|g)++ on *-apple-darwin* after revision 186978 dominiq at lps dot ens.fr
2012-10-14 20:29 ` howarth at nitro dot med.uc.edu
2012-10-17 20:46 ` dominiq at lps dot ens.fr
2012-10-17 21:04 ` howarth at nitro dot med.uc.edu
2012-10-17 21:18 ` howarth at nitro dot med.uc.edu
2012-10-17 23:06 ` howarth at nitro dot med.uc.edu
2012-10-17 23:15 ` howarth at nitro dot med.uc.edu
2012-10-17 23:58 ` howarth at nitro dot med.uc.edu [this message]
2012-10-18 0:16 ` howarth at nitro dot med.uc.edu
2012-10-18 0:24 ` howarth at nitro dot med.uc.edu
2012-10-18 0:25 ` howarth at nitro dot med.uc.edu
2012-10-18 0:29 ` howarth at nitro dot med.uc.edu
2012-10-27 11:31 ` iains at gcc dot gnu.org
2012-10-27 16:34 ` howarth at bromo dot med.uc.edu
2012-12-06 16:43 ` rguenth at gcc dot gnu.org
2012-12-06 17:41 ` howarth at nitro dot med.uc.edu
2012-12-06 17:49 ` howarth at nitro dot med.uc.edu
2012-12-06 17:55 ` howarth at nitro dot med.uc.edu
2012-12-07 13:50 ` dominiq at lps dot ens.fr
2012-12-07 14:53 ` howarth at bromo dot med.uc.edu
2012-12-11 8:55 ` jakub at gcc dot gnu.org
2012-12-11 15:53 ` dominiq at lps dot ens.fr
2012-12-11 20:37 ` dominiq at lps dot ens.fr
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-54404-4-o0L4OkYP80@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).