From: Michael Jeanson <mjeanson@ubuntu.com>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Cc: Debian m68k <debian-68k@lists.debian.org>,
Linux/m68k <linux-m68k@vger.kernel.org>
Subject: Re: gcc possibly generating invalid assembler
Date: Thu, 20 Apr 2017 17:00:35 -0400 [thread overview]
Message-ID: <87479900-ca57-fd8c-bd74-004ec5db2a29@ubuntu.com> (raw)
On Thu, Apr 13, 2017 at 01:08:59PM +0200, John Paul Adrian Glaubitz wrote:
>
> I have unsuccessfully been trying to build liburcu on Debian/m68k. After
> adding "m68k" as a detected architecture in configure.ac, the build
> fails with the assembler generating syntax error messages [1]:
>
> gcc -DHAVE_CONFIG_H -I. -I../.. -I../../urcu -Wdate-time -D_FORTIFY_SOURCE=2 -I../.. -I../.. -I../../tests/common -g -g -O2
> -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -pthread -c -o test_urcu_defer.o test_urcu_defer.c
> /tmp/ccXHVXOc.s: Assembler messages:
> /tmp/ccXHVXOc.s:312: Error: syntax error -- statement `add.l %d1,nr_writes@TLSLE+4(%a0)' ignored
> /tmp/ccXHVXOc.s:440: Error: syntax error -- statement `add.l %d1,nr_writes@TLSLE+4(%a0)' ignored
The invalid asm is related to Thread Local Storage and liburcu has a
compat layer that can be enabled at configure for platforms that don't
have it.
With './configure --disable-compiler-tls' the build succeeds and the
regression test suite completes without having to disable optimisations.
Hope this helps,
Michael
next reply other threads:[~2017-04-20 21:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-20 21:00 Michael Jeanson [this message]
2017-04-20 21:43 ` gcc possibly generating invalid assembler Wouter Verhelst
-- strict thread matches above, loose matches on Subject: below --
2017-04-13 11:08 John Paul Adrian Glaubitz
2017-04-14 7:36 ` Wouter Verhelst
2017-04-18 18:42 ` John Paul Adrian Glaubitz
2017-04-19 7:39 ` Wouter Verhelst
2017-04-19 7:46 ` John Paul Adrian Glaubitz
2017-04-19 7:51 ` Wouter Verhelst
2017-04-19 8:38 ` Wouter Verhelst
2017-04-17 20:01 ` Richard Z
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=87479900-ca57-fd8c-bd74-004ec5db2a29@ubuntu.com \
--to=mjeanson@ubuntu.com \
--cc=debian-68k@lists.debian.org \
--cc=glaubitz@physik.fu-berlin.de \
--cc=linux-m68k@vger.kernel.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