public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/52878] [4.8 regression] bootstrap failure: "MASK_LONG_DOUBLE_128" redefined
Date: Wed, 18 Apr 2012 21:06:00 -0000	[thread overview]
Message-ID: <bug-52878-4-msgRaPaQh8@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52878-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #9 from H.J. Lu <hjl.tools at gmail dot com> 2012-04-18 21:04:37 UTC ---
(In reply to comment #8)
> > If someone can provide a description of what TARGET_LONG_DOUBLE_128
> > should be in all cases, I can try to come up with a patch.
> 
> It should be:
> 
> options.h:#define MASK_LONG_DOUBLE_128 (1 << 16)
> options.h:#define TARGET_LONG_DOUBLE_128 ((target_flags & MASK_LONG_DOUBLE_128)
> != 0)
> 
> on SPARC/Solaris, but of course the (1 << 16) is dependent on other options, so
> a patch that hardcodes it isn't acceptable, IOW this must be fixed in
> opth-gen.awk.

For a target which doesn't use long-double-switch.opt, will
TARGET_LONG_DOUBLE_128 be a fixed value? If no, how is its
value determined? If yes, what is the fixed value?


  parent reply	other threads:[~2012-04-18 21:06 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-05 15:44 [Bug bootstrap/52878] New: sparc64 " jamborm at gcc dot gnu.org
2012-04-05 16:11 ` [Bug bootstrap/52878] " hjl.tools at gmail dot com
2012-04-06  6:38 ` [Bug bootstrap/52878] [4.8 regression] " ebotcazou at gcc dot gnu.org
2012-04-06 12:24 ` hjl.tools at gmail dot com
2012-04-16  7:14 ` mikpe at it dot uu.se
2012-04-18 16:42 ` mikpe at it dot uu.se
2012-04-18 17:24 ` ebotcazou at gcc dot gnu.org
2012-04-18 17:35 ` hjl.tools at gmail dot com
2012-04-18 21:01 ` ebotcazou at gcc dot gnu.org
2012-04-18 21:06 ` hjl.tools at gmail dot com [this message]
2012-04-18 21:19 ` ebotcazou at gcc dot gnu.org
2012-04-18 21:43 ` hjl.tools at gmail dot com
2012-04-19  0:14 ` hjl.tools at gmail dot com
2012-04-19  8:42 ` ebotcazou at gcc dot gnu.org
2012-04-19 17:18 ` hjl.tools at gmail dot com
2012-04-20 20:16 ` mikpe at it dot uu.se
2012-04-23 23:21 ` rth at gcc dot gnu.org
2012-04-23 23:33 ` hjl at gcc dot gnu.org
2012-05-26 13:49 ` ebotcazou 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-52878-4-msgRaPaQh8@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).