public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/48949] [4.6/4.7 Regression] gcc-4.6.0 regression with complex.h on i386-pc-solaris2.10
Date: Sat, 14 Jan 2012 10:35:00 -0000	[thread overview]
Message-ID: <bug-48949-4-xVkdHKI8Zq@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-48949-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #9 from Jakub Jelinek <jakub at gcc dot gnu.org> 2012-01-14 10:20:34 UTC ---
(In reply to comment #8)
> > Please answer comment #3.
> 
> Answers provided on bug report 50944.

Clearly the system complex.h is being used, does that mean that the header
hasn't been fixincluded at all?  The diff is against a wrong header, you are
diffing system complex.h against C++.
Can you look into your logs if you have message like:
Applying solaris_complex          to complex.h
in your build log?  Can you look into your build tree if you have
gcc/include-fixed/complex.h
header?  Did it get installed?
/usr/local/gcc-4.6.0/x86_64-SunOS-core2/lib/gcc/i386-pc-solaris2.10/4.6.0/include-fixed/complex.h
would be the installed location of the file.


  parent reply	other threads:[~2012-01-14 10:21 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-10 15:37 [Bug c/48949] New: " mariah.lenox at gmail dot com
2011-05-10 15:47 ` [Bug c/48949] " mariah.lenox at gmail dot com
2011-05-10 16:02 ` [Bug target/48949] [4.6/4.7 Regression] " jsm28 at gcc dot gnu.org
2011-05-19 12:56 ` jakub at gcc dot gnu.org
2011-06-27 16:27 ` jakub at gcc dot gnu.org
2011-10-10 11:50 ` rguenth at gcc dot gnu.org
2011-11-01 18:18 ` ebotcazou at gcc dot gnu.org
2011-11-01 18:18 ` ebotcazou at gcc dot gnu.org
2011-11-02 13:19 ` mariah.lenox at gmail dot com
2012-01-12 20:26 ` pinskia at gcc dot gnu.org
2012-01-14 10:35 ` jakub at gcc dot gnu.org [this message]
2012-01-19 12:37 ` rguenth at gcc dot gnu.org
2012-01-19 21:37 ` mariah.lenox at gmail dot com
2012-01-19 22:03 ` mariah.lenox at gmail dot com
2012-01-19 22:15 ` jakub at gcc dot gnu.org
2012-03-01 15:21 ` jakub at gcc dot gnu.org
2013-04-12 15:18 ` [Bug target/48949] [4.7/4.8/4.9 " jakub at gcc dot gnu.org
2013-12-11 15:15 ` 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-48949-4-xVkdHKI8Zq@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).