public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hp at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/61548] [5 Regression] FAIL: gcc.dg/tls/alias-1.c (internal compiler error)
Date: Sun, 08 Feb 2015 14:03:00 -0000	[thread overview]
Message-ID: <bug-61548-4-0x7tqwjtIn@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-61548-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61548

Hans-Peter Nilsson <hp at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|FIXED                       |---

--- Comment #24 from Hans-Peter Nilsson <hp at gcc dot gnu.org> ---
Apparently the test still fails, so I'm re-opening it as wrongly closed, since
it still fails for arm-eabi and cris-elf (same as in comment #23) and according
to <https://gcc.gnu.org/ml/gcc-testresults/2015-02/msg00812.html> also for
hppa64-hp-hpux11.11.  The error changed from ICE to something else but that is
not a reason to close the PR.

Comment #23 isn't clear that the assembler complains and that the relevant part
of gcc.log is:

output is:
/tmp/ccDUW6dB.s: Assembler messages:
/tmp/ccDUW6dB.s:37: Error: symbol `___emutls_v.foo' is already defined

Assembler code will be attached.


  parent reply	other threads:[~2015-02-08 14:03 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-18 10:29 [Bug regression/61548] New: " ktkachov at gcc dot gnu.org
2014-06-23 14:54 ` [Bug regression/61548] " jgreenhalgh at gcc dot gnu.org
2014-06-23 14:54 ` jgreenhalgh at gcc dot gnu.org
2014-06-23 14:57 ` jgreenhalgh at gcc dot gnu.org
2014-06-23 18:19 ` hp at gcc dot gnu.org
2014-06-23 22:27 ` hubicka at gcc dot gnu.org
2014-06-24  8:23 ` jgreenhalgh at gcc dot gnu.org
2014-07-23  4:49 ` pinskia at gcc dot gnu.org
2014-07-23  4:49 ` [Bug regression/61548] [4.10 Regression] " pinskia at gcc dot gnu.org
2014-07-23  5:00 ` tony.wang at arm dot com
2014-11-19 13:49 ` [Bug ipa/61548] [5 " rguenth at gcc dot gnu.org
2014-11-19 13:52 ` ktkachov at gcc dot gnu.org
2014-12-01 12:27 ` rguenth at gcc dot gnu.org
2015-01-14 12:31 ` ramana at gcc dot gnu.org
2015-01-16  6:28 ` hubicka at gcc dot gnu.org
2015-01-16  9:55 ` ktkachov at gcc dot gnu.org
2015-01-23 22:05 ` tbsaunde at gcc dot gnu.org
2015-01-26  3:56 ` hubicka at ucw dot cz
2015-01-26 10:05 ` tbsaunde+mozilla at tbsaunde dot org
2015-02-01 21:24 ` hubicka at gcc dot gnu.org
2015-02-02 23:31 ` tbsaunde at gcc dot gnu.org
2015-02-05  0:11 ` hubicka at gcc dot gnu.org
2015-02-05  3:58 ` hubicka at gcc dot gnu.org
2015-02-05  4:02 ` hubicka at gcc dot gnu.org
2015-02-05  4:15 ` tbsaunde at tbsaunde dot org
2015-02-05  4:46 ` hubicka at gcc dot gnu.org
2015-02-05  4:46 ` hubicka at gcc dot gnu.org
2015-02-06 15:53 ` ktkachov at gcc dot gnu.org
2015-02-08 14:03 ` hp at gcc dot gnu.org [this message]
2015-02-08 14:04 ` hp at gcc dot gnu.org
2015-02-08 22:21 ` [Bug ipa/61548] [5 Regression] FAIL: gcc.dg/tls/alias-1.c hubicka at gcc dot gnu.org
2015-02-08 22:52 ` hubicka at gcc dot gnu.org
2015-02-09 12:00 ` hp at gcc dot gnu.org
2015-02-09 21:07 ` hubicka at gcc dot gnu.org
2015-02-09 21:09 ` hubicka at gcc dot gnu.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-61548-4-0x7tqwjtIn@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).