public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/63966] [5 regression] inconsistent operand constraints compiling build libcpp
Date: Wed, 19 Nov 2014 14:58:00 -0000 [thread overview]
Message-ID: <bug-63966-4-LfmNWXccgO@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-63966-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63966
--- Comment #2 from Uroš Bizjak <ubizjak at gmail dot com> ---
What happens if you remove check for __PIC__ from the #if guard?
>From gcc-bugs-return-467509-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Nov 19 15:03:02 2014
Return-Path: <gcc-bugs-return-467509-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 2223 invoked by alias); 19 Nov 2014 15:03:02 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 2116 invoked by uid 55); 19 Nov 2014 15:02:53 -0000
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/63966] [5 regression] inconsistent operand constraints compiling build libcpp
Date: Wed, 19 Nov 2014 15:03:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ro at CeBiTec dot Uni-Bielefeld.DE
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 5.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-63966-4-u9vZv8gcxA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-63966-4@http.gcc.gnu.org/bugzilla/>
References: <bug-63966-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-11/txt/msg01981.txt.bz2
Content-length: 408
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63966
--- Comment #3 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> ---
> --- Comment #2 from Uroš Bizjak <ubizjak at gmail dot com> ---
> What happens if you remove check for __PIC__ from the #if guard?
Which guard do you mean? There's no such guard in either libcpp/lex.c
or cpuid.h, only in driver-i386.c.
Rainer
>From gcc-bugs-return-467510-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Nov 19 15:07:44 2014
Return-Path: <gcc-bugs-return-467510-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 5156 invoked by alias); 19 Nov 2014 15:07:44 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 5133 invoked by uid 48); 19 Nov 2014 15:07:40 -0000
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/63966] [5 regression] inconsistent operand constraints compiling build libcpp
Date: Wed, 19 Nov 2014 15:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ubizjak at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 5.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-63966-4-lmY2gCxB6S@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-63966-4@http.gcc.gnu.org/bugzilla/>
References: <bug-63966-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-11/txt/msg01982.txt.bz2
Content-length: 494
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63966
--- Comment #4 from Uroš Bizjak <ubizjak at gmail dot com> ---
(In reply to ro@CeBiTec.Uni-Bielefeld.DE from comment #3)
> > --- Comment #2 from Uroš Bizjak <ubizjak at gmail dot com> ---
> > What happens if you remove check for __PIC__ from the #if guard?
>
> Which guard do you mean? There's no such guard in either libcpp/lex.c
> or cpuid.h, only in driver-i386.c.
Oh, I was looking to driver-i386.c, this one is in lex.c
>From gcc-bugs-return-467511-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Nov 19 15:08:16 2014
Return-Path: <gcc-bugs-return-467511-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 5914 invoked by alias); 19 Nov 2014 15:08:16 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 5866 invoked by uid 48); 19 Nov 2014 15:08:13 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/61384] [5 Regression] ICE on valid code at -O3 on x86_64-linux-gnu
Date: Wed, 19 Nov 2014 15:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 5.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-61384-4-luFVEA103P@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-61384-4@http.gcc.gnu.org/bugzilla/>
References: <bug-61384-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-11/txt/msg01983.txt.bz2
Content-length: 166
https://gcc.gnu.org/bugzilla/show_bug.cgi?ida384
--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Seems this got fixed or made latent by r217303.
next prev parent reply other threads:[~2014-11-19 14:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-19 14:41 [Bug bootstrap/63966] New: " ro at gcc dot gnu.org
2014-11-19 14:41 ` [Bug bootstrap/63966] " ro at gcc dot gnu.org
2014-11-19 14:48 ` [Bug target/63966] " rguenth at gcc dot gnu.org
2014-11-19 14:58 ` ubizjak at gmail dot com [this message]
2014-11-19 19:28 ` ubizjak at gmail dot com
2014-11-19 21:03 ` ro at CeBiTec dot Uni-Bielefeld.DE
2014-11-20 10:09 ` jakub at gcc dot gnu.org
2014-11-20 10:44 ` uros at gcc dot gnu.org
2014-11-20 10:50 ` ubizjak at gmail dot com
2014-11-20 11:02 ` ubizjak at gmail dot com
2014-11-20 11:08 ` jakub at gcc dot gnu.org
2014-11-20 11:10 ` ubizjak at gmail dot com
2014-11-20 12:10 ` uros at gcc dot gnu.org
2014-11-20 12:15 ` ubizjak at gmail dot com
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-63966-4-LfmNWXccgO@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).