From: Alexey Neyman <stilor@att.net>
To: crossgcc@sourceware.org
Subject: [crosstool-ng/crosstool-ng] bd2a37: gcc: backport fix for xtensa PR target/78603
Date: Thu, 01 Dec 2016 04:46:00 -0000 [thread overview]
Message-ID: <583fab01748d3_50483f87d160513882591@hookshot-fe3-cp1-prd.iad.github.net.mail> (raw)
[-- Attachment #1: Type: text/plain, Size: 1445 bytes --]
Branch: refs/heads/master
Home: https://github.com/crosstool-ng/crosstool-ng
Commit: bd2a376fe371094c7599186a508a698c9226315c
https://github.com/crosstool-ng/crosstool-ng/commit/bd2a376fe371094c7599186a508a698c9226315c
Author: Max Filippov <jcmvbkbc@gmail.com>
Date: 2016-11-30 (Wed, 30 Nov 2016)
Changed paths:
A patches/gcc/5.4.0/878-xtensa-Fix-PR-target-78603.patch
A patches/gcc/6.2.0/872-xtensa-Fix-PR-target-78603.patch
Log Message:
-----------
gcc: backport fix for xtensa PR target/78603
This fixes the following kind of ICE on configurations with zero
overhead loops support:
../src/pjlib-test/thread.c: In function 'thread_test':
../src/pjlib-test/thread.c:328:1: internal compiler error: in
dwarf2out_var_location, at dwarf2out.c:21846
Signed-off-by: Max Filippov <jcmvbkbc@gmail.com>
Commit: 6785440c767c7c0411bbe6e89d60320b8b8161cd
https://github.com/crosstool-ng/crosstool-ng/commit/6785440c767c7c0411bbe6e89d60320b8b8161cd
Author: Alexey Neyman <stilor@att.net>
Date: 2016-11-30 (Wed, 30 Nov 2016)
Changed paths:
A patches/gcc/5.4.0/878-xtensa-Fix-PR-target-78603.patch
A patches/gcc/6.2.0/872-xtensa-Fix-PR-target-78603.patch
Log Message:
-----------
Merge pull request #486 from jcmvbkbc/xtensa-fix-pr78603
gcc: backport fix for xtensa PR target/78603
Compare: https://github.com/crosstool-ng/crosstool-ng/compare/f849de0de38b...6785440c767c
[-- Attachment #2: Type: text/plain, Size: 71 bytes --]
--
For unsubscribe information see http://sourceware.org/lists.html#faq
reply other threads:[~2016-12-01 4:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=583fab01748d3_50483f87d160513882591@hookshot-fe3-cp1-prd.iad.github.net.mail \
--to=stilor@att.net \
--cc=crossgcc@sourceware.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).