public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "i.palachev at samsung dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/61192] Conflict between register and function name for lto on sparc
Date: Mon, 20 Oct 2014 11:24:00 -0000 [thread overview]
Message-ID: <bug-61192-4-hHtZtVVeAl@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-61192-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61192
Ilya Palachev <i.palachev at samsung dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |i.palachev at samsung dot com
--- Comment #2 from Ilya Palachev <i.palachev at samsung dot com> ---
(In reply to Daniel Cederman from comment #0)
> when using lto on sparc.
Daniel, can you also provide original source code (not preprocessed)? It's
interesting whether this error can be reproduced on other arhictectures.
next prev parent reply other threads:[~2014-10-20 11:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-15 9:53 [Bug lto/61192] New: " cederman at gaisler dot com
2014-05-15 10:05 ` [Bug lto/61192] " rguenth at gcc dot gnu.org
2014-10-20 11:24 ` i.palachev at samsung dot com [this message]
2014-10-20 14:48 ` cederman at gaisler dot com
2021-12-24 10:32 ` [Bug middle-end/61192] " pinskia at gcc dot gnu.org
2021-12-24 10:34 ` [Bug middle-end/61192] Conflict between global register and function name pinskia at gcc dot gnu.org
2023-10-18 18:54 ` pinskia at gcc dot gnu.org
2023-10-18 18:55 ` pinskia 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-61192-4-hHtZtVVeAl@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).