public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "raphael.jakse at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/31782] Invalid assembly code on initial dollar signs
Date: Sun, 22 Jun 2014 08:42:00 -0000 [thread overview]
Message-ID: <bug-31782-4-Hhvm7wFoc3@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-31782-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=31782
Raphaël JAKSE <raphael.jakse at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |raphael.jakse at gmail dot com
--- Comment #6 from Raphaël JAKSE <raphael.jakse at gmail dot com> ---
New information on this bug:
With gcc version 4.8.3-3 on Debian x86-64 targeting x86_64-linux-gnu, trying to
get the assembly version of the following code with gcc -S:
void $() {}
void a() { $(); }
I get:
[...]
call $
[...]
With clang, I get:
[...]
callq ($)
[...]
Making the corresponding object file of this code with gcc -c
- succeed with the assembly code generated by clang
- fails with the assembly code generated by gcc with the following message:
t.c: Assembler messages:
t.c:30: Error: missing or invalid immediate expression `'
Adding parentheses in the assembly code generated by gcc:
call $ → call ($)
make the object file generation succeed.
Clang seems to add parentheses whenever the function name starts with a dollar
sign ($).
>From gcc-bugs-return-454660-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jun 22 09:17:53 2014
Return-Path: <gcc-bugs-return-454660-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 9904 invoked by alias); 22 Jun 2014 09:17:52 -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 9772 invoked by uid 55); 22 Jun 2014 09:17:15 -0000
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/61503] RTL representation of i386 shrdl instruction is incorrect?
Date: Sun, 22 Jun 2014 09:17: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: 4.10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: glisse at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-61503-4-jU4fek1aN7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-61503-4@http.gcc.gnu.org/bugzilla/>
References: <bug-61503-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-06/txt/msg01742.txt.bz2
Content-length: 506
https://gcc.gnu.org/bugzilla/show_bug.cgi?ida503
--- Comment #1 from Marc Glisse <glisse at gcc dot gnu.org> ---
Author: glisse
Date: Sun Jun 22 09:16:35 2014
New Revision: 211873
URL: https://gcc.gnu.org/viewcvs?rev!1873&root=gcc&view=rev
Log:
2014-06-22 Marc Glisse <marc.glisse@inria.fr>
PR target/61503
* config/i386/i386.md (x86_64_shrd, x86_shrd,
ix86_rotr<dwi>3_doubleword): Replace ashiftrt with lshiftrt.
Modified:
trunk/gcc/ChangeLog
trunk/gcc/config/i386/i386.md
next prev parent reply other threads:[~2014-06-22 8:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-31782-4@http.gcc.gnu.org/bugzilla/>
2011-02-04 16:42 ` funto66 at gmail dot com
2014-06-22 8:42 ` raphael.jakse at gmail dot com [this message]
2014-06-22 11:27 ` harald at gigawatt dot nl
2014-06-23 7:25 ` raphael.jakse at gmail dot com
2014-06-23 21:36 ` harald at gigawatt dot nl
2014-06-24 7:37 ` raphael.jakse at gmail dot com
2021-07-29 23:45 ` pinskia at gcc dot gnu.org
2021-07-29 23:46 ` pinskia at gcc dot gnu.org
2021-07-29 23:46 ` pinskia at gcc dot gnu.org
2021-08-03 1:18 ` pinskia at gcc dot gnu.org
2024-04-02 21:01 ` pinskia at gcc dot gnu.org
2007-05-02 2:20 [Bug c/31782] New: " truedfx at gentoo dot org
2007-05-02 2:33 ` [Bug target/31782] " pinskia at gcc dot gnu dot org
2007-05-02 4:58 ` truedfx at gentoo dot org
2007-05-02 11:58 ` joseph at codesourcery 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-31782-4-Hhvm7wFoc3@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).