public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/63691] GCC 4.9.x fails to build GLIBC 2.20 on HPPA
Date: Fri, 31 Oct 2014 00:49:00 -0000 [thread overview]
Message-ID: <bug-63691-4-nZ9aDM430C@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-63691-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63691
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |INVALID
--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
this was a bug in glibc iirc. it showed up on aarch64 too. there is two ways
of solving it, backport the patch to glibc or define trap pattern in the pa
backend.
next prev parent reply other threads:[~2014-10-31 0:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-30 21:19 [Bug target/63691] New: " aaro.koskinen at iki dot fi
2014-10-30 21:27 ` [Bug target/63691] " aaro.koskinen at iki dot fi
2014-10-31 0:29 ` dave.anglin at bell dot net
2014-10-31 0:49 ` pinskia at gcc dot gnu.org [this message]
2014-10-31 1:18 ` pinskia at gcc dot gnu.org
2014-10-31 18:43 ` aaro.koskinen at iki dot fi
2014-10-31 19:43 ` dave.anglin at bell dot net
2014-10-31 21:52 ` aaro.koskinen at iki dot fi
2014-11-01 8:17 ` schwab@linux-m68k.org
2014-11-01 11:32 ` aaro.koskinen at iki dot fi
2014-11-01 14:34 ` danglin at gcc dot gnu.org
2014-11-04 19:36 ` aaro.koskinen at iki dot fi
2021-11-28 14:43 ` danglin 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-63691-4-nZ9aDM430C@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).