public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mikestump at comcast dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/46912] [4.6 Regression] Test failures for  g++.dg/plugin/*plugin*.C on powerpc-apple-darwin9
Date: Thu, 16 Dec 2010 21:59:00 -0000	[thread overview]
Message-ID: <bug-46912-4-P6CqK956np@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-46912-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46912

--- Comment #3 from Mike Stump <mikestump at comcast dot net> 2010-12-16 21:59:44 UTC ---
> it's all fall-out from the different assumed sizes of Bool (see also 46902).

?  bool/_Bool is 4 on pcc.  Making it any other size introduces a abi bug. 
What code assumes _Bool is 1 byte?  That would be the root cause that needs
fixing.


> I think (subject to Mike's agreement) that, since Darwin's <stdbool.h> does not
> set bool to int for GCC > 3

You're misreading it:

$ cat  t.c
int sz = sizeof(_Bool);
$ gcc -arch ppc t.c -S -o -
    .machine ppc7400
_sz:
    .long    4

> .. that we should default to one byte bools on PPC darwin (there is no effect on x86).

No, that would be bad.


  parent reply	other threads:[~2010-12-16 21:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-12 17:47 [Bug testsuite/46912] New: " dominiq at lps dot ens.fr
2010-12-13  8:26 ` [Bug testsuite/46912] " iains at gcc dot gnu.org
2010-12-14 21:45 ` iains at gcc dot gnu.org
2010-12-16 21:59 ` mikestump at comcast dot net [this message]
2010-12-16 22:06 ` iains at gcc dot gnu.org
2010-12-16 22:42 ` mikestump at comcast dot net
2011-01-03 19:58 ` rguenth at gcc dot gnu.org
2011-01-03 21:00 ` rguenth at gcc dot gnu.org
2011-01-03 21:54 ` iains at gcc dot gnu.org
2011-01-09 13:02 ` iains at gcc dot gnu.org
2011-01-09 13:11 ` 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-46912-4-P6CqK956np@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).