public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/65836] [6 Regression] gnat fails to build on aarch64-linux-gnu
Date: Sun, 26 Apr 2015 11:19:00 -0000 [thread overview]
Message-ID: <bug-65836-4-YmedQDYRoc@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65836-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65836
vries at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |vries at gcc dot gnu.org
--- Comment #6 from vries at gcc dot gnu.org ---
Possibly a duplicate of(In reply to Andrew Pinski from comment #2)
> This might be the same bug as 65824.
For now I'm assuming this is a duplicate of PR65824, which I just marked as a
duplicate of PR65818 (for which a patch has been proposed).
prev parent reply other threads:[~2015-04-26 11:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-65836-4@http.gcc.gnu.org/bugzilla/>
2015-04-21 17:04 ` ktkachov at gcc dot gnu.org
2015-04-21 17:06 ` pinskia at gcc dot gnu.org
2015-04-22 8:54 ` rguenth at gcc dot gnu.org
2015-04-22 9:07 ` ktkachov at gcc dot gnu.org
2015-04-22 13:35 ` ktkachov at gcc dot gnu.org
2015-04-22 13:54 ` ktkachov at gcc dot gnu.org
2015-04-26 11:19 ` vries at gcc dot gnu.org [this message]
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-65836-4-YmedQDYRoc@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).