On Thu, Feb 1, 2018 at 2:44 AM, Jeff Law wrote:
>
> This is V2 of the patch to fix 84128.
>
> What's change since V1. The -fstack-check path for non-linux systems
> has been restored to its previous (correct) behavior. Only the behavior
> for -fstack-check on linux systems and
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83705
Janne Blomqvist changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
On Tue, Jan 30, 2018 at 12:53 PM, Koval, Julia wrote:
> Thank you for your comments, fixed them and rebased Ice Lake patch on top of
> it. Ok for trunk?
>
> Bitmask patch changelog:
>
> gcc/c-family/
> * c-common.h (omp_clause_mask): Move to wide_int_bitmask.h.
>
>
On Thu, Feb 1, 2018 at 1:16 AM, H.J. Lu wrote:
>
> We currently read and write beyond the builtin jmpbuf on ILP32 targets
> where Pmode == DImode and ptr_mode == SImode. Since the builtin jmpbuf
> is an array of 5 pointers, ptr_mode should be used to save and restore
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84156
Dominique d'Humieres changed:
What|Removed |Added
Priority|P3 |P4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83705
--- Comment #8 from Janne Blomqvist ---
Author: jb
Date: Thu Feb 1 07:41:03 2018
New Revision: 257281
URL: https://gcc.gnu.org/viewcvs?rev=257281=gcc=rev
Log:
PR 83705 Repeat with large values
This patch fixes the regression by increasing the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84157
Uroš Bizjak changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84160
Marek Polacek changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84088
Tom de Vries changed:
What|Removed |Added
Keywords||wrong-code
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84160
Marek Polacek changed:
What|Removed |Added
Keywords||ice-on-valid-code
CC|
On 01/31/2018 09:34 PM, Paul Richard Thomas wrote:
This fixes the reduced testcase provided by Tom de Vries in comment #7
of the PR. Committed as 'obvious' as r257262. Will await a report from
Tom as to whether or not this fixes the original problem
Hi Paul,
it does.
I've tested
/gcc/gcc-trunk/libexec/gcc/x86_64-pc-linux-gnu/8.0.1/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: ../gcc-source-trunk/configure --enable-languages=c,c++,lto
--prefix=/home/su/software/tmp/gcc/gcc-trunk --disable-bootstrap
Thread model: posix
gcc version 8.0.1 20180131 (experimental) [trunk
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84159
Bug ID: 84159
Summary: filesystem::path::operator/= with has root directory
path
Product: gcc
Version: 8.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84155
Dominique d'Humieres changed:
What|Removed |Added
Keywords||wrong-code
Priority|P3
Hi Richard,
On 31 January 2018 at 21:39, Richard Biener wrote:
> On Wed, Jan 31, 2018 at 11:28 AM, Kugan Vivekanandarajah
> wrote:
>> Hi Richard,
>>
>> Thanks for the review.
>> On 25 January 2018 at 20:04, Richard Biener
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84153
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83503
--- Comment #16 from Martin Sebor ---
(In reply to Jason Merrill from comment #4)
Jason, I'm only starting to look into it but if I understand your suggestion
correctly, I don't think the bug can be fixed by relying on attribute
exclusions.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83503
Martin Sebor changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84158
Martin Sebor changed:
What|Removed |Added
Keywords||diagnostic
Known to work|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84158
Bug ID: 84158
Summary: missing -Wreturn-type due to incorrect handling of
attributes for template specializations
Product: gcc
Version: 8.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84153
Brett Neumeier changed:
What|Removed |Added
Status|RESOLVED|UNCONFIRMED
Resolution|INVALID
This is V2 of the patch to fix 84128.
What's change since V1. The -fstack-check path for non-linux systems
has been restored to its previous (correct) behavior. Only the behavior
for -fstack-check on linux systems and -fstack-clash-protection has been
changed.
This patch to the Go frontend changes value methods to always check
that the pointer they are passed is not nil. We already dereference
the pointer to copy the value, but if the method does not use the
value then the pointer dereference may be optimized away. Do an
explicit nil check so that we
On 01/31/2018 03:41 AM, Uros Bizjak wrote:
>>
>> The one concern I have is do we need to tell the CFI machinery that
>> %eax's value was restored to its entry value?
>
> Can you or someone that knows CFI stuff please investigate this a bit?
> I'm not expert in this area, and I don't feel
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84113
--- Comment #15 from Douglas Mencken ---
another question: what is so special with "darwin" (besides that long story
when apple ditched gcc due to gpl v3 and created llvm'n'stuff which is still
unavail for powerpc) to have all these
On 01/31/2018 10:36 AM, Renlin Li wrote:
Hi there,
I have a patch to fix to regressions we observed in armhf native
environment.
To effectively check out of range for format string, a target type
should be
used. And according to the standard, int type is used for "width" and
"precision"
field
We currently read and write beyond the builtin jmpbuf on ILP32 targets
where Pmode == DImode and ptr_mode == SImode. Since the builtin jmpbuf
is an array of 5 pointers, ptr_mode should be used to save and restore
frame and program pointers. Since x86 only saves stack pointer in
stack save area,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84155
--- Comment #5 from Dominique d'Humieres ---
Also caused by r257065 as pr84141.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84141
--- Comment #18 from Dominique d'Humieres ---
> I get the ICE with r257065.
r257064 is OK.
This patch to libbacktrace closes any debuginfo files that we opened.
Bootstrapped and ran libbacktrace tests on x86_64-pc-linux-gnu. This
should fix https://golang.org/issue/23626. Committed to mainline.
Ian
2018-01-31 Ian Lance Taylor
* elf.c (elf_add): Close descriptor
This patch teaches install_parm_decl (part of the PTX .param
optimization during omp-lowering) not to extract the identifier string
of artificial decls. Apparently, GCC's OpenACC testsuite did not have
any tests that contained local arrays which used alloca for storage
allocation, or else this
On Wed, Jan 31, 2018 at 10:18:46PM +0200, Janne Blomqvist wrote:
> This patch fixes the regression by increasing the limit where we fall
> back to runtime to 2**28 elements, which is the same limit where
> previous releases failed. The are still bugs in the runtime
> evaluation, so in many cases
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84155
Thomas Koenig changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84157
--- Comment #2 from Tom de Vries ---
Created attachment 43315
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=43315=edit
lrand48.c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84157
--- Comment #1 from Tom de Vries ---
Regression caused by r257270.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84157
Bug ID: 84157
Summary: [8 Regression] [nvptx] ICE: RTL check: expected code
'reg', have 'lshiftrt'
Product: gcc
Version: 8.0
Status: UNCONFIRMED
Severity:
On 01/31/2018 01:28 AM, Eric Botcazou wrote:
>> -fstack-check and -fstack-clash both potentially create a loop for stack
>> probing. In that case they both need a scratch register to hold the
>> loop upper bound.
>>
>> The code to allocate a scratch register first starts with the
>> caller-saved
Snapshot gcc-6-20180131 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/6-20180131/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 6 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches/gcc-6
On 01/31/2018 10:33 PM, Segher Boessenkool wrote:
Hi!
On Wed, Jan 31, 2018 at 08:47:08PM +0100, Uros Bizjak wrote:
We should skip RTXes that will result in certain ICE here, and this is
what the attached patch does.
2018-01-31 Uros Bizjak
PR target/84123
*
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83993
Jakub Jelinek changed:
What|Removed |Added
Summary|[7/8 Regression] ICE: |[7 Regression] ICE:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84116
Jakub Jelinek changed:
What|Removed |Added
Keywords||ice-on-invalid-code
While refining the COMDAT group on Solaris 10 patch
https://gcc.gnu.org/ml/gcc-patches/2018-01/msg02257.html
I noticed that the comdat_group effective-target keyword didn't work
when using Solaris as. No wonder, actually, given the different
syntaxes used:
* with sparc as
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84156
Thomas Koenig changed:
What|Removed |Added
Target Milestone|--- |8.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81779
Marek Polacek changed:
What|Removed |Added
Summary|[6/7/8 Regression] bool |[6/7 Regression] bool
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84156
Bug ID: 84156
Summary: [8 Regression] valgrind error with print *,1
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81779
--- Comment #2 from Marek Polacek ---
Author: mpolacek
Date: Wed Jan 31 22:12:46 2018
New Revision: 257271
URL: https://gcc.gnu.org/viewcvs?rev=257271=gcc=rev
Log:
PR c/81779
* c-parser.c (c_parser_compound_statement_nostart):
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84155
Thomas Koenig changed:
What|Removed |Added
Target Milestone|--- |8.0
--- Comment #3 from Thomas Koenig
On Wed, 31 Jan 2018, Marek Polacek wrote:
> This fixes one particular instance of the "tokens coming from system headers
> may
> suppress a warning" problem. While we need a more general solution, for GCC 8
> we can at least fix this spot.
>
> Bootstrapped/regtested on x86_64-linux, ok for
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84141
--- Comment #17 from Jürgen Reuter ---
Maybe also look at the PR84155 with a similar (possibly the same?) problem, and
a workaround, or a direct case for the culprit in a single line.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84141
--- Comment #16 from Thomas Koenig ---
This is strange.
Looking at the small reproducer and grepping for the settings to dtype
with
diff -b -u repro.f90.old repro.f90.new |grep 'dtype.*='
where repro.f90.old is the output of
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84123
--- Comment #5 from uros at gcc dot gnu.org ---
Author: uros
Date: Wed Jan 31 21:37:54 2018
New Revision: 257270
URL: https://gcc.gnu.org/viewcvs?rev=257270=gcc=rev
Log:
PR rtl-optimization/84123
* combine.c (change_zero_ext):
Hi!
On Wed, Jan 31, 2018 at 08:47:08PM +0100, Uros Bizjak wrote:
> We should skip RTXes that will result in certain ICE here, and this is
> what the attached patch does.
>
> 2018-01-31 Uros Bizjak
>
> PR target/84123
> * combine.c (change_zero_ext): Check if hard
This fixes one particular instance of the "tokens coming from system headers may
suppress a warning" problem. While we need a more general solution, for GCC 8
we can at least fix this spot.
Bootstrapped/regtested on x86_64-linux, ok for trunk?
2018-01-31 Marek Polacek
Hi!
We ICE on the following test because rest_of_insert_endbranch
separates a setjmp call from the following NOTE_INSN_CALL_ARG_LOCATION
that must always immediately follow the call.
No other note or debug insn (which aren't around after var-tracking anyway)
needs to follow the call, so the loop
Hi!
Some spots in the vectorizer create generic COND_EXPRs that in one of the
branches compute some +/-/* arithmetics. When -ftrapv, the gimplifier
ICEs on this as it may trap, we can't emit code with multiple basic blocks
from the APIs and don't want to evaluate it if the guarding condition is
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80867
kelvin at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |RESOLVED
Hi!
If the gfc_match_omp_variable_list calls fail, they don't modify head,
so *head means referencing NULL. In that case we don't really need to
free anything, nothing has been allocated, just need to emit a syntax error.
Bootstrapped/regtested on x86_64-linux and i686-linux, committed to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84116
--- Comment #3 from Jakub Jelinek ---
Author: jakub
Date: Wed Jan 31 20:47:48 2018
New Revision: 257266
URL: https://gcc.gnu.org/viewcvs?rev=257266=gcc=rev
Log:
PR fortran/84116
* openmp.c (gfc_match_omp_clauses): If all the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84150
--- Comment #3 from H.J. Lu ---
Created attachment 43314
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=43314=edit
A patch
I am testing this.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83993
--- Comment #8 from Jakub Jelinek ---
Author: jakub
Date: Wed Jan 31 20:46:36 2018
New Revision: 257265
URL: https://gcc.gnu.org/viewcvs?rev=257265=gcc=rev
Log:
PR c++/83993
* constexpr.c (cxx_eval_outermost_constant_expr):
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83993
--- Comment #7 from Jakub Jelinek ---
Author: jakub
Date: Wed Jan 31 20:45:41 2018
New Revision: 257264
URL: https://gcc.gnu.org/viewcvs?rev=257264=gcc=rev
Log:
PR c++/83993
* constexpr.c (diag_array_subscript): Emit different
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84155
--- Comment #2 from Jürgen Reuter ---
This regression has been also introduced within revisions r256722 and r257131.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81084
Andrew Jenner changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81084
Andrew Jenner changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84155
--- Comment #1 from Jürgen Reuter ---
Created attachment 43313
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=43313=edit
Reproducer, 48 lines
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81084
--- Comment #13 from Andrew Jenner ---
Created attachment 43312
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=43312=edit
Patch in progress so far
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84155
Bug ID: 84155
Summary: [8.0 Regression] program hangs on valid code
Product: gcc
Version: 8.0.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84141
--- Comment #15 from Jürgen Reuter ---
Created attachment 43311
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=43311=edit
Isolated file: small reproducer, 250 lines
This should print
1: 2: INSIDE MCI_VAMP_WRITE
VAMP integrator:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70589
Michael Meissner changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79038
Michael Meissner changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
This fixes the reduced testcase provided by Tom de Vries in comment #7
of the PR. Committed as 'obvious' as r257262. Will await a report from
Tom as to whether or not this fixes the original problem
Paul
2018-01-31 Paul Thomas
PR fortran/84088
* trans-expr.c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84088
--- Comment #11 from Paul Thomas ---
Author: pault
Date: Wed Jan 31 20:28:35 2018
New Revision: 257262
URL: https://gcc.gnu.org/viewcvs?rev=257262=gcc=rev
Log:
2018-01-31 Paul Thomas
PR fortran/84088
*
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84154
--- Comment #1 from Michael Meissner ---
Created attachment 43310
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=43310=edit
Example code to show the problem.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84154
Bug ID: 84154
Summary: PowerPC GCC 7 and 8 have regression in converting fp
to short/char and returning it
Product: gcc
Version: 8.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83987
Volker Reichelt changed:
What|Removed |Added
Summary|[6/7 Regression] ICE with |[6/7/8 Regression] ICE with
Hello world,
I have just committed the attached patch as obvious and simple.
Before, the C binding label was ignored for generating
function prototypes with the -fc-prototypes option.
2018-01-31 Thomas Koenig
* dump-parse-tree.c (write_proc): Use sym_name (which
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84152
David Malcolm changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
This patch fixes the regression by increasing the limit where we fall
back to runtime to 2**28 elements, which is the same limit where
previous releases failed. The are still bugs in the runtime
evaluation, so in many cases longer characters will still fail, so
print a warning message.
Regtested
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84141
--- Comment #14 from Dominique d'Humieres ---
I get the ICE with r257065.
Hi again,
On 24/01/2018 16:58, Paolo Carlini wrote:
Hi,
I'm looking into this rather mild regression, which should be
relatively easy to fix. In short, Jason's fix for c++/54325 moved an
abstract_virtuals_error_sfinae check from build_aggr_init_expr to
build_cplus_new therefore the testcase
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83926
--- Comment #9 from Peter Bergner ---
So the problem is that the splitter for vsx_div_v2di unconditionally calls
gen_divdi3() , which assumes we have a 64-bit integer HW div insn. If you do a
scalar 64-bit div, we notice we don't have that HW
Hi,
The vec-cmpne-long.c tests targets -mcpu=power8, but always dg-do-run, even
on P7 (or earlier) systems. Add a dg-do run requirement for p8vector_hw to
prevent illegal instruction errors.
(noticed during review of test results from a P7).
Sniff tests look good.
OK for trunk?
Hello!
As shown in the PR, alpha specific testcase hits the above ICE when
combine pass is trying to simplify:
(insn 13 12 16 2 (set (reg:SI 141 [ ID ])
(zero_extend:SI (subreg:QI (reg:DI 48 $f16 [ ID ]) 0))) 48
{zero_extendqisi2}
via change_zero_ext (combine.c):
11486 else if
Hi,
I just committed the patch below as obvious.
Index: ChangeLog
===
--- ChangeLog (revision 257256)
+++ ChangeLog (working copy)
@@ -1,5 +1,10 @@
2018-01-31 Janne Blomqvist
+ * trans-const.c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84113
--- Comment #14 from Douglas Mencken ---
(In reply to Jakub Jelinek from comment #13)
> No, it means anybody can fix it, just the release will not be blocked if it
> is not fixed.
Well, nice. May I fix it? What happened between 6.4 and 7.1?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84113
--- Comment #13 from Jakub Jelinek ---
No, it means anybody can fix it, just the release will not be blocked if it is
not fixed.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82641
--- Comment #27 from Arnd Bergmann ---
(In reply to Richard Earnshaw from comment #26)
> (In reply to Arnd Bergmann from comment #25)
>
> > or to apply more force and add the ".arch" to each inline
> > asm individually.
>
> No, that would not
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84153
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84013
--- Comment #2 from Katsunori Kumatani ---
I'm not familiar with tree-ssa-structalias, but it appears to me that the "fix"
is quite simple? Or am I missing something? Here's the snippet from it, updated
with my attempt:
if (restrict_var)
Hi,
Noticed during a review of test results on an AIX platform, a few
of the (p9 target specific) tests are expecting to see Power9 codegen, but
are failing to build due to the environment missing P9 assembler support. Thus,
we need to add the power9_vector_ok test requirement to these tests.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84113
--- Comment #12 from Douglas Mencken ---
(In reply to Segher Boessenkool from comment #11)
> It will be fixed. But not many people have access to powerpc-darwin systems
> to test on.
I prefer “would” before “will”, and I may give an access to
On Wed, Jan 31, 2018 at 11:11 AM, augustine.sterl...@gmail.com
wrote:
> On Tue, Jan 30, 2018 at 8:02 PM, Max Filippov wrote:
>>
>> libgcc/
>> 2018-01-31 Max Filippov
>>
>> * config/xtensa/ieee754-df.S
On Tue, Jan 30, 2018 at 8:02 PM, Max Filippov wrote:
>
> libgcc/
> 2018-01-31 Max Filippov
>
> * config/xtensa/ieee754-df.S (__adddf3_aux): Add
> .literal_position directive.
> * config/xtensa/ieee754-sf.S (__addsf3_aux):
Segher Boessenkool writes:
> Hi!
>
> On Fri, Jan 26, 2018 at 01:25:51PM +, Richard Sandiford wrote:
>>if (SCALAR_INT_MODE_P (inmode))
>> new_out_reg = gen_lowpart_SUBREG (outmode, reg);
>>else
>> -new_out_reg = gen_rtx_SUBREG
Eric Botcazou writes:
>> Tested on SPARC64/Linux and ARM/EABI, applied on mainline and 7 branch.
>
> As discussed in the audit trail, this beefs up the internal documentation
> about WORD_REGISTER_OPERATIONS.
>
> Tested with 'make doc', applied on mainline and 7 branch.
>
The following patch fixes ICE for
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82444
The patch was successfully bootstrapped on x86_64.
Committed as rev. 257254.
Index: ChangeLog
===
--- ChangeLog (revision 257252)
+++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84153
Bug ID: 84153
Summary: Bootstrap failure when using dependency libraries in
non-system location
Product: gcc
Version: 7.3.0
Status: UNCONFIRMED
Severity:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84113
--- Comment #11 from Segher Boessenkool ---
It will be fixed. But not many people have access to powerpc-darwin systems
to test on.
Does this still happen on trunk as well?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82444
--- Comment #1 from Vladimir Makarov ---
Author: vmakarov
Date: Wed Jan 31 19:03:11 2018
New Revision: 257254
URL: https://gcc.gnu.org/viewcvs?rev=257254=gcc=rev
Log:
2018-01-31 Vladimir Makarov
PR target/82444
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80867
--- Comment #13 from kelvin at gcc dot gnu.org ---
Author: kelvin
Date: Wed Jan 31 18:56:11 2018
New Revision: 257252
URL: https://gcc.gnu.org/viewcvs?rev=257252=gcc=rev
Log:
gcc/ChangeLog:
2018-01-31 Richard Biener
1 - 100 of 275 matches
Mail list logo