public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fthain at telegraphics dot com.au" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/46179] New: Codegen/TLS: invalid assembler syntax
Date: Tue, 26 Oct 2010 03:33:00 -0000	[thread overview]
Message-ID: <bug-46179-4@http.gcc.gnu.org/bugzilla/> (raw)

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

           Summary: Codegen/TLS: invalid assembler syntax
           Product: gcc
           Version: 4.5.2
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: fthain@telegraphics.com.au
            Target: m68k-linux-gnu


Created attachment 22157
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=22157
pre-processed source from gen_uuid.c from util-linux

gcc version 4.5.2 20101021 (prerelease) (GCC)

$ m68k-linux-gnu-gcc -c gen_uuid.i -O2   
/tmp/cceVtxzz.s: Assembler messages:
/tmp/cceVtxzz.s:709: Error: syntax error -- statement `move.l
%d1,last.5137@TLSLE+4(%a0)' ignored
/tmp/cceVtxzz.s:886: Error: syntax error -- statement `move.l
%d1,last.5137@TLSLE+4(%a0)' ignored

Some background may be found here (relating to debian's gcc-4.4 package which
has TLS backported):
http://lists.debian.org/debian-68k/2010/10/msg00037.html
(In that compiler, the code generated is an offset against TLSLDO, but shows
the same bug.)

The bug was initially filed for binutils (since closed as invalid):
http://sourceware.org/bugzilla/show_bug.cgi?id=12157

Bug may be worked around with -O0.


             reply	other threads:[~2010-10-26  3:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-26  3:33 fthain at telegraphics dot com.au [this message]
2010-10-26 21:04 ` [Bug target/46179] " schwab@linux-m68k.org
2010-10-26 22:14 ` mkuvyrkov at gcc dot gnu.org
2010-10-27  0:47 ` fthain at telegraphics dot com.au
2010-10-27  8:41 ` schwab@linux-m68k.org
2010-10-27 13:28 ` fthain at telegraphics dot com.au
2010-10-28 15:21 ` fthain at telegraphics dot com.au
2010-10-28 15:34 ` fthain at telegraphics dot com.au
2010-11-01 16:08 ` tg at mirbsd dot org
2010-11-04 13:12 ` mkuvyrkov at gcc dot gnu.org
2010-11-04 16:27 ` tg at mirbsd dot org
2010-12-12 14:04 ` schwab at gcc dot gnu.org
2010-12-12 14:09 ` schwab@linux-m68k.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-46179-4@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).