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/65644] Assembler errors on Solaris 10 x86-64: `(%eXX)' is not a valid 64 bit base/index expression
Date: Wed, 01 Apr 2015 08:01:00 -0000 [thread overview]
Message-ID: <bug-65644-4-IPS1e3lHQB@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65644-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65644
--- Comment #3 from Uroš Bizjak <ubizjak at gmail dot com> ---
(In reply to Jakub Jelinek from comment #2)
> impossible, and the addr32 pieces in e.g. ix86_decompose_address would need
> to be disabled based on some configure macro.
In this case, a better place for the test is just after
/* Index and base should have the same mode. */
check in ix86_legitimate_address_p.
>From gcc-bugs-return-482464-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Apr 01 08:02:40 2015
Return-Path: <gcc-bugs-return-482464-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 63332 invoked by alias); 1 Apr 2015 08:02:40 -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 63291 invoked by uid 48); 1 Apr 2015 08:02:36 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/65646] [5 Regression] ICE in invalid syntax
Date: Wed, 01 Apr 2015 08:02:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
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-65646-4-fpD8q9Oo4T@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-65646-4@http.gcc.gnu.org/bugzilla/>
References: <bug-65646-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: 2015-04/txt/msg00016.txt.bz2
Content-length: 151
https://gcc.gnu.org/bugzilla/show_bug.cgi?ide646
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Started with r213641. Reducing.
next prev parent reply other threads:[~2015-04-01 8:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-01 3:09 [Bug target/65644] New: " skunk at iskunk dot org
2015-04-01 7:35 ` [Bug target/65644] " ubizjak at gmail dot com
2015-04-01 7:43 ` jakub at gcc dot gnu.org
2015-04-01 8:01 ` ubizjak at gmail dot com [this message]
2015-04-01 13:39 ` ro at CeBiTec dot Uni-Bielefeld.DE
2015-04-01 14:14 ` ubizjak at gmail dot com
2015-04-02 20:31 ` skunk at iskunk dot org
2015-04-06 20:29 ` skunk at iskunk dot org
2015-04-07 14:33 ` ro at CeBiTec dot Uni-Bielefeld.DE
2015-04-08 5:38 ` skunk at iskunk dot org
2015-04-08 9:43 ` ro at CeBiTec dot Uni-Bielefeld.DE
2015-04-09 21:56 ` skunk at iskunk dot 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-65644-4-IPS1e3lHQB@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).