public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <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: Tue, 07 Apr 2015 14:33:00 -0000	[thread overview]
Message-ID: <bug-65644-4-Qn1mBPgeg9@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 #8 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> ---
> --- Comment #7 from Daniel Richard G. <skunk at iskunk dot org> ---
> Reopening due to lack of resolution.
>
> If system patches should resolve the issue, then I am open to trying any that
> are appropriate; if they work, then they can be noted in the documentation. But
> it is also possible that this is a limitation of this particular version of
> Solaris that cannot be patched, and thus will need a workaround in GCC.

Looking closer, you are *not* using the Solaris assembler (/usr/ccs/bin/as):

    {standard input}: Assembler messages:
    {standard input}:233: Error: `(%esi)' is not a valid 64 bit base/index
expression
    {standard input}:250: Error: `(%edx)' is not a valid 64 bit base/index
expression
    {standard input}:1150: Error: `(%edx)' is not a valid 64 bit base/index
expression

as cannot read from standard input, and doesn't contain the messages you
cite, while gas does.

To reproduce this, you need to provide much more information:

* How exactly was gcc configured?

* Please provide the output of

  gcc -v -m64 -O -c gcc-asm-bug.c

  for your testcase?

It might that the assembler used at configure and compile time differs,
e.g. you configured gcc to use as, but somehow it finds gas instead at
compile time.

    Rainer


  parent reply	other threads:[~2015-04-07 14:33 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
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 [this message]
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-Qn1mBPgeg9@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).