public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jbglaw@lug-owl.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/52023] [C11] _Alignof (double) yields wrong value on x86
Date: Tue, 14 Jan 2014 10:31:00 -0000	[thread overview]
Message-ID: <bug-52023-4-rYHuGEsnHD@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52023-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #17 from Jan-Benedict Glaw <jbglaw@lug-owl.de> ---
(In reply to Marek Polacek from comment #16)
> >     tree field = build_decl (UNKNOWN_LOCATION, FIELD_DECL, NULL_TREE,
> >          ^
> > cc1plus: all warnings being treated as errors
> 
> Should be fixed now.

No, not yet. The most recent build for powerpc64-darwin done by my build robot
still faces this warning and thus breaks:

http://toolchain.lug-owl.de/buildbot/show_build_details.php?id=89063

-->
http://toolchain.lug-owl.de/buildbot/deliver_artifact.php?mode=view&id=733877

So what shall we do with this? The macro is called with two arguments, of which
one ("field") isn't used. Just mark it as unused or (void)-cast it away?


  parent reply	other threads:[~2014-01-14 10:31 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-27 20:06 [Bug c/52023] New: " eggert at gnu dot org
2012-01-27 20:12 ` [Bug target/52023] " pinskia at gcc dot gnu.org
2012-01-27 21:10 ` bruno at clisp dot org
2012-01-27 21:39 ` pinskia at gcc dot gnu.org
2012-01-27 21:43 ` pinskia at gcc dot gnu.org
2012-01-27 21:44 ` pinskia at gcc dot gnu.org
2012-01-27 21:54 ` eggert at gnu dot org
2012-01-27 21:54 ` pinskia at gcc dot gnu.org
2012-01-27 22:39 ` eggert at gnu dot org
2012-01-27 23:12 ` bruno at clisp dot org
2012-01-27 23:30 ` joseph at codesourcery dot com
2012-01-27 23:37 ` joseph at codesourcery dot com
2012-01-30 11:15 ` [Bug c/52023] [C11] " rguenth at gcc dot gnu.org
2013-12-04 22:57 ` jsm28 at gcc dot gnu.org
2013-12-04 22:59 ` jsm28 at gcc dot gnu.org
2013-12-04 23:00 ` jsm28 at gcc dot gnu.org
2013-12-05  9:56 ` jbglaw@lug-owl.de
2013-12-05 12:08 ` mpolacek at gcc dot gnu.org
2014-01-14 10:31 ` jbglaw@lug-owl.de [this message]
2014-01-14 11:50 ` jakub 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-52023-4-rYHuGEsnHD@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).