public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug objc/45989] Some objc.dg-struct-layout-encoding-1 tests XPASS Date: Fri, 07 Jan 2011 19:39:00 -0000 [thread overview] Message-ID: <bug-45989-4-to2BXWhxOV@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-45989-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45989 --- Comment #8 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> 2011-01-07 19:16:42 UTC --- > --- Comment #7 from Dominique d'Humieres <dominiq at lps dot ens.fr> 2011-01-05 22:31:14 UTC --- >> * We should use i?86*-*-* (or perhaps just i?86-*-*, I see no reason for the >> first *). > > I don't think this cover x86_64-*-*, this is why I have tested *86*-*-* Indeed, had forgotten about that. In that case, we should do as everywhere else in the testsuite and explicitly list i?86-*-* and x86_64-*-*. Just *86*-*-* is too general (there was a sparcle86 or something, I think :-). >> * The comment should be updated (perhaps with PR #s) to provide documentation >> for the XFAILed changes. > > See the end of comment #2. This should probably addressed by the objc > maintainers. Probably, and hopefully the will do so once we finally propose the patch and get approval. With the exception of x86_64 handling above, we're good to go, I think. Rainer
next prev parent reply other threads:[~2011-01-07 19:16 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-10-12 18:11 [Bug objc/45989] New: " ro at gcc dot gnu.org 2010-11-23 10:01 ` [Bug objc/45989] " nicola at gcc dot gnu.org 2010-12-21 18:21 ` dominiq at lps dot ens.fr 2010-12-22 15:47 ` dominiq at lps dot ens.fr 2011-01-05 14:05 ` dominiq at lps dot ens.fr 2011-01-05 19:17 ` ro at gcc dot gnu.org 2011-01-05 19:31 ` ro at gcc dot gnu.org 2011-01-05 22:51 ` dominiq at lps dot ens.fr 2011-01-07 19:39 ` ro at CeBiTec dot Uni-Bielefeld.DE [this message] 2011-01-09 12:34 ` dominiq at lps dot ens.fr 2011-01-14 17:37 ` ro at gcc dot gnu.org 2011-01-14 18:55 ` ro at gcc dot gnu.org 2011-01-14 19:05 ` ro at gcc dot gnu.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-45989-4-to2BXWhxOV@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).