public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "raj.khem at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/94249] [10 regression] Many -flto -fuse-linker-plugin tests FAIL: could not add symbols
Date: Wed, 01 Apr 2020 17:25:32 +0000 [thread overview]
Message-ID: <bug-94249-4-hvdzqovstb@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94249-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94249
--- Comment #20 from Khem Raj <raj.khem at gmail dot com> ---
(In reply to CVS Commits from comment #18)
> The master branch has been updated by Martin Liska <marxin@gcc.gnu.org>:
>
> https://gcc.gnu.org/g:142d68f50b48309f48e34fc1d9d6dbbeecfde684
>
> commit r10-7492-g142d68f50b48309f48e34fc1d9d6dbbeecfde684
> Author: Martin Liska <mliska@suse.cz>
> Date: Wed Apr 1 09:37:37 2020 +0200
>
> Fix typo in a macro usage.
>
> PR lto/94249
> * plugin-api.h: Fix a typo.
this patch seems to be causing gcc ICE on ARM when compiling lz4 sources in
kernel, lz4, vlc almost identical ICE is seen
attached is the test case please compile it with -O3
during GIMPLE pass: vect
lz4.c: In function 'LZ4_compress_fast_extState':
lz4.c:1180:5: internal compiler error: Segmentation fault
1180 | int LZ4_compress_fast_extState(void* state, const char* source, char*
dest, int inputSize, int maxOutputSize, int acceleration)
| ^~~~~~~~~~~~~~~~~~~~~~~~~~
Please submit a full bug report,
next prev parent reply other threads:[~2020-04-01 17:25 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-21 12:40 [Bug lto/94249] New: " ro at gcc dot gnu.org
2020-03-21 12:40 ` [Bug lto/94249] " ro at gcc dot gnu.org
2020-03-21 17:44 ` marxin at gcc dot gnu.org
2020-03-21 18:12 ` ro at CeBiTec dot Uni-Bielefeld.DE
2020-03-21 21:13 ` danglin at gcc dot gnu.org
2020-03-22 8:53 ` marxin at gcc dot gnu.org
2020-03-22 9:28 ` ro at CeBiTec dot Uni-Bielefeld.DE
2020-03-22 17:55 ` marxin at gcc dot gnu.org
2020-03-22 18:56 ` ro at CeBiTec dot Uni-Bielefeld.DE
2020-03-22 21:05 ` ro at CeBiTec dot Uni-Bielefeld.DE
2020-03-23 1:15 ` dave.anglin at bell dot net
2020-03-23 9:06 ` marxin at gcc dot gnu.org
2020-03-23 17:37 ` danglin at gcc dot gnu.org
2020-03-23 19:04 ` dave.anglin at bell dot net
2020-03-24 10:40 ` cvs-commit at gcc dot gnu.org
2020-03-24 10:41 ` marxin at gcc dot gnu.org
2020-03-24 17:05 ` cvs-commit at gcc dot gnu.org
2020-03-24 17:08 ` cvs-commit at gcc dot gnu.org
2020-03-24 17:10 ` cvs-commit at gcc dot gnu.org
2020-04-01 7:37 ` cvs-commit at gcc dot gnu.org
2020-04-01 17:25 ` raj.khem at gmail dot com
2020-04-01 17:25 ` raj.khem at gmail dot com [this message]
2020-04-02 11:07 ` marxin at gcc dot gnu.org
2020-04-02 13:41 ` raj.khem at gmail dot com
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-94249-4-hvdzqovstb@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).