https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69264
Richard Biener changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79219
--- Comment #1 from Richard Biener ---
So you mean DW/W -> W, but that can result in the result being not
representable?
What's the desired behavior in this case? Invoking undefined behavior?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67328
Yuri Gribov changed:
What|Removed |Added
CC||tetra2005 at gmail dot com
--- Comment #4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60913
--- Comment #7 from Chris ---
Damian, can you tell me where in the standard allocatable polymorphic results
are prohibited with pure functions? I've been using them that way in my code,
which compiles without issue using gfortran. I haven't teste
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79216
Richard Biener changed:
What|Removed |Added
CC||ebotcazou at gcc dot gnu.org
--- Commen
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79224
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |7.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79224
Bug ID: 79224
Summary: [7 Regression] Large C-Ray slowdown
Product: gcc
Version: 7.0
Status: UNCONFIRMED
Keywords: missed-optimization
Severity: normal
Priority
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79212
Richard Biener changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79219
--- Comment #2 from Uroš Bizjak ---
(In reply to Richard Biener from comment #1)
> So you mean DW/W -> W, but that can result in the result being not
> representable?
> What's the desired behavior in this case? Invoking undefined behavior?
x86
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77333
--- Comment #11 from Tony Kelman ---
Thank you!
-fno-devirtualize on its own did not help.
-fno-ipa-cp on its own did fix the problem.
Adding -fno-ipa-cp only when compiling
lib/Transforms/Vectorize/SLPVectorizer.cpp was enough to fix the prob
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79219
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79061
--- Comment #20 from Tobias Burnus ---
Created attachment 40574
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=40574&action=edit
New still failing test case (tar.gz), slightly modifying the previous one
(In reply to chefmax from comment #1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77333
--- Comment #12 from Tony Kelman ---
Output of dump options uploaded here (8.2 MB file):
https://github.com/tkelman/docker-gcc-bisect/raw/07f6fa56e2f6d60ff90613b9c036f830fb8a422a/LLVMVectorize.tar.gz
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78363
--- Comment #9 from Richard Biener ---
Author: rguenth
Date: Wed Jan 25 09:48:10 2017
New Revision: 244892
URL: https://gcc.gnu.org/viewcvs?rev=244892&root=gcc&view=rev
Log:
2017-01-25 Richard Biener
PR debug/78363
* omp-expa
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78363
Richard Biener changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79061
--- Comment #21 from Maxim Ostapenko ---
(In reply to Tobias Burnus from comment #20)
> Created attachment 40574 [details]
> New still failing test case (tar.gz), slightly modifying the previous one
>
> (In reply to chefmax from comment #19)
> >
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79212
--- Comment #2 from davids at gcc dot gnu.org ---
Created attachment 40575
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=40575&action=edit
Simple openmp test case that exposes the ICE
Compile the test with "gfortran -fopenmp"
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79212
ktkachov at gcc dot gnu.org changed:
What|Removed |Added
Keywords||ice-on-valid-code
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70607
Jonathan Wakely changed:
What|Removed |Added
Known to work||4.4.7
Summary|The return ty
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79224
Martin Liška changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79224
--- Comment #2 from Martin Liška ---
r244884 (current trunk): 2409 milliseconds
r240470 (25 Sep 2016): 2309 milliseconds
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79224
--- Comment #3 from Martin Liška ---
Just for curiosity, all releases:
4.7.0 (93c5ebd73a4d1626)(22 Mar 2012 07:11): [took: 2.836s] result: OK
Rendering took: 2 seconds (2531 milliseconds)
4.7.1 (0e3097e7d505b7be)(14 Jun 2012 08:32): [took: 2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78529
--- Comment #29 from Jan Hubicka ---
I think the official answer for LTOing symbols implementing runtime (i.e. those
that can be introduced by middle-end) is "don't do that". We may support LTOing
them with an explicit attribute "used" on them or
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56671
Richard Biener changed:
What|Removed |Added
CC||rguenth at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79225
Bug ID: 79225
Summary: Memory hog for large initializers
Product: gcc
Version: 7.0
Status: UNCONFIRMED
Keywords: memory-hog
Severity: normal
Priority: P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79225
Richard Biener changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56671
İsmail Dönmez changed:
What|Removed |Added
CC||ismail at i10z dot com
--- Comment #8 fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70831
Jan Hubicka changed:
What|Removed |Added
CC||enkovich.gnu at gmail dot com,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=0
Nick Clifton changed:
What|Removed |Added
Status|NEW |ASSIGNED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79176
Jan Hubicka changed:
What|Removed |Added
CC||jason at redhat dot com
--- Comment #3 fro
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61791
Jonathan Wakely changed:
What|Removed |Added
Last reconfirmed|2015-04-09 00:00:00 |2017-1-25
--- Comment #3 from Jonathan
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79061
--- Comment #22 from Tobias Burnus ---
(In reply to Maxim Ostapenko from comment #21)
> Strange, new testcase (with strdup) doesn't fail for me:
[...]
That's odd; I re-check with your options (except that g++ 7 is here in the
PATH) and I still s
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79226
Bug ID: 79226
Summary: Additional overloads needed for __complex__ types
Product: gcc
Version: 6.3.1
Status: UNCONFIRMED
Keywords: rejects-valid
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79145
--- Comment #6 from ktkachov at gcc dot gnu.org ---
Author: ktkachov
Date: Wed Jan 25 11:10:30 2017
New Revision: 244894
URL: https://gcc.gnu.org/viewcvs?rev=244894&root=gcc&view=rev
Log:
[ARM] PR target/79145 Fix xordi3 expander for immediate op
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79145
ktkachov at gcc dot gnu.org changed:
What|Removed |Added
Known to work||7.0
Summary|[5/6
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79227
Bug ID: 79227
Summary: Questionable -Wmisleading-indentation diagnostic in
HSAIL-Tools
Product: gcc
Version: 6.2.0
Status: UNCONFIRMED
Severity: minor
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79228
Bug ID: 79228
Summary: __complex__ extension interferes with C++14 UDLs for
std::complex
Product: gcc
Version: 6.3.1
Status: UNCONFIRMED
Keywords: rejects-valid
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=25621
--- Comment #15 from Richard Biener ---
On trunk only the cost model prevents vectorization of the s32 loop now (with
generic tuning/arch). With core-avx2 I get for both innermost loops
.L6:
addl$1, %r10d
vmovapd (%rbx,%r8),
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79228
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79226
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79228
--- Comment #2 from Richard Biener ---
We have -fext-numeric-literals which we could disable by default (and the user
can switch that back on for backward compatibility). Of course that not only
guards 'i'...
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79216
Eric Botcazou changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=39838
Jan Hubicka changed:
What|Removed |Added
Status|ASSIGNED|NEW
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79046
--- Comment #12 from Jakub Jelinek ---
Author: jakub
Date: Wed Jan 25 11:54:36 2017
New Revision: 244895
URL: https://gcc.gnu.org/viewcvs?rev=244895&root=gcc&view=rev
Log:
PR other/79046
* configure.ac: Add GCC_BASE_VER.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79216
--- Comment #7 from Eric Botcazou ---
> As in, I would expect that:
>
> struct foo __attribute__((scalar_storage_order("big-endian")))
> {
> uint32_t bar;
> } foo;
>
> uint32_t *baz = &foo.bar;
>
> ... would give an error on a littleendian
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=39838
amker at gcc dot gnu.org changed:
What|Removed |Added
CC||amker at gcc dot gnu.org
--- C
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=39838
--- Comment #24 from amker at gcc dot gnu.org ---
(In reply to amker from comment #23)
> I can also confirm Os is fixed on trunk @244877 using reported command line,
> while O2 goes up to 76 now.
on arm (with -march=armv5te -mthumb -mthumb-interw
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70465
Jakub Jelinek changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79061
--- Comment #23 from Tobias Burnus ---
(In reply to Tobias Burnus from comment #22)
> As I recently did some incremental builds, I will retry it after a full
> bootstrap.
Didn't make a difference - I still see the ASAN run-time fail. I wonder wh
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79229
Bug ID: 79229
Summary: [7.0.1 regression] ICE in gfc_trans_assignment_1 with
-fcheck=mem
Product: gcc
Version: 7.0.1
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79229
Jürgen Reuter changed:
What|Removed |Added
Keywords||ice-on-valid-code
--- Comment #1 from Jü
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69264
--- Comment #5 from Richard Biener ---
Author: rguenth
Date: Wed Jan 25 12:30:41 2017
New Revision: 244897
URL: https://gcc.gnu.org/viewcvs?rev=244897&root=gcc&view=rev
Log:
2017-01-25 Richard Biener
PR tree-optimization/69264
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70768
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #9
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70929
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79061
--- Comment #24 from Maxim Ostapenko ---
(In reply to Tobias Burnus from comment #23)
> (In reply to Tobias Burnus from comment #22)
> > As I recently did some incremental builds, I will retry it after a full
> > bootstrap.
>
> Didn't make a dif
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79212
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70768
--- Comment #10 from Jakub Jelinek ---
When comparing r224581 (the first cc1plus that doesn't ICE on the gcc5
preprocessed source) with r244763 cc1plus on the same source (though, both are
checking builds), the latter eats less memory, not more.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79212
--- Comment #5 from davids at gcc dot gnu.org ---
(In reply to Jakub Jelinek from comment #4)
> Started with r233913, I'll have a look.
Hi Jakub, just to let you know I posted a possible fix for 7.0 release on the
mailing list yesterday if you wa
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=76957
Richard Biener changed:
What|Removed |Added
CC||amker at gcc dot gnu.org
--- Comment #7
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79229
Martin Liška changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=72850
Richard Biener changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=72850
--- Comment #8 from Richard Biener ---
Author: rguenth
Date: Wed Jan 25 13:14:41 2017
New Revision: 244898
URL: https://gcc.gnu.org/viewcvs?rev=244898&root=gcc&view=rev
Log:
2017-01-25 Richard Biener
PR testsuite/72850
* gcc.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69264
Richard Biener changed:
What|Removed |Added
Known to work||7.0
Summary|[5/6/7 regressio
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78985
--- Comment #7 from Martin Liška ---
On aarch64 r242068 (Date: Fri Nov 11 12:53:36 2016 +)
fails with error in gcc/config/aarch64/cortex-a57-fma-steering.c.
I'm going to test merge base of gcc-6-branch and current trunk.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79229
Richard Biener changed:
What|Removed |Added
Priority|P3 |P4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70929
--- Comment #5 from Richard Biener ---
I wonder why we don't simply do the following, which checks the type of the
originally built CALL_EXPR from the frontends which should have done the
job of matching up the actual arguments closely enough wit
Hi,
I would like to report a bug in GCC. However, can't create a user in
the bug report system.
Any suggestions?
Here are some more details:
i can't create a new account here:
https://gcc.gnu.org/bugzilla/createaccount.cgi
It say something like :
"User account creation filtered due to spam."
A
On 2017.01.25 at 15:43 +0200, Oren Twaig wrote:
> Hi,
>
> I would like to report a bug in GCC. However, can't create a user in
> the bug report system.
> Any suggestions?
>
> Here are some more details:
>
> i can't create a new account here:
> https://gcc.gnu.org/bugzilla/createaccount.cgi
>
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71290
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #5
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77468
--- Comment #21 from PeteVine ---
It would be great if https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53659 could
get squashed in one fell swoop.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71374
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71463
Jakub Jelinek changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53659
James Greenhalgh changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68664
James Greenhalgh changed:
What|Removed |Added
CC||siarhei.siamashka at gmail dot
com
-
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79173
--- Comment #4 from Vincent Lefèvre ---
Also, make sure that the optimization is still done when a variable is a
constant or replaced by a constant (with Clang, the optimization is no longer
done in such a case).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68664
James Greenhalgh changed:
What|Removed |Added
Target|powerpc*-*-*, aarch64*-*-* |powerpc*-*-*, aarch64*-*-*,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=76957
--- Comment #8 from amker at gcc dot gnu.org ---
I will have a look. Thanks.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79224
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78559
--- Comment #11 from Bernd Schmidt ---
Looks like other_insn is only used for cases where we rewrite cc sets in this
way, so Bin's patch does look reasonably narrow. We could maybe record the CC
reg being changed and only discard reg notes, but i
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78559
--- Comment #12 from Bernd Schmidt ---
Sorry, long pause while editing that comment made me leave out part of what I
was trying to say - I meant only discard notes that reference the CC reg. But
it seems an unnecessary complication.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61791
--- Comment #4 from Jonathan Wakely ---
Author: redi
Date: Wed Jan 25 15:01:05 2017
New Revision: 244900
URL: https://gcc.gnu.org/viewcvs?rev=244900&root=gcc&view=rev
Log:
PR libstdc++/70607 make proj(T) and conj(T) return complex
PR li
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=72758
tnfchris at gcc dot gnu.org changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
CC
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70607
--- Comment #7 from Jonathan Wakely ---
Author: redi
Date: Wed Jan 25 15:01:05 2017
New Revision: 244900
URL: https://gcc.gnu.org/viewcvs?rev=244900&root=gcc&view=rev
Log:
PR libstdc++/70607 make proj(T) and conj(T) return complex
PR li
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79082
--- Comment #9 from Franz Sirl ---
With r244892 and -O2 -Wformat-truncation=2 I nearly get the warnings I expect.
What remains is case 3, but this seems to be a small deficiency in VRP. For the
term I used ((val < 0) ? -(val % 100) : (val % 100
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70607
Jonathan Wakely changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61791
Jonathan Wakely changed:
What|Removed |Added
Keywords||rejects-valid
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79227
--- Comment #1 from David Malcolm ---
Some notes:
There are 7 cases in the reproducer, but it only warns for the 3rd case (lines
34-35).
In each of the 7 cases in the reproducer, NEXT_STMT_LOC and BODY_LOC are on the
same line:
/* If NEXT_ST
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77914
--- Comment #6 from Jakub Jelinek ---
Created attachment 40578
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=40578&action=edit
gcc7-pr77914.patch
So like this (untested)?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78337
Jakub Jelinek changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78896
--- Comment #2 from Jakub Jelinek ---
Jason, any thoughts on this? Shall we just disallow lambdas in decompositions?
Shall the standard say anything about those?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79227
--- Comment #2 from David Malcolm ---
Created attachment 40579
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=40579&action=edit
Patch to tweak Wmisleading indentation
This patch removes the "(guard_exploc.line == body_exploc.line)" conditi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79218
--- Comment #2 from Bill Schmidt ---
At the moment, swap optimization doesn't attempt to handle __int128 values, for
which swaps don't deal with elements of a vector, but pieces of a cohesive
integer value. This may be overly conservative, and w
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79061
--- Comment #25 from Tobias Burnus ---
(In reply to Maxim Ostapenko from comment #24)
> Perhaps you use strict_init_order=true option (e.g.
> ASAN_OPTIONS=check_initialization_order=true:report_globals=3:
> strict_init_order=true)?
strict_init_
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53659
--- Comment #8 from Siarhei Siamashka ---
Since my report predates bug 68664 by several years, shouldn't bug 68664 be a
duplicate? In addition, my report was much more detailed, since it also
provided a practical use case, showcasing the importan
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64697
--- Comment #18 from Václav Haisman ---
And I have just verified it is still the same with GCC 6.3.0.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79082
--- Comment #10 from Martin Sebor ---
Only three out of the five patches for bug 78703 have been committed. I'm
still waiting for approval of the substantive patch 4, and patch 5 depends on
it. With those committed I think the warning should be
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78896
--- Comment #3 from Jason Merrill ---
(In reply to Jakub Jelinek from comment #2)
> Jason, any thoughts on this? Shall we just disallow lambdas in
> decompositions? Shall the standard say anything about those?
Yes, the standard should probably
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77914
--- Comment #7 from Jason Merrill ---
(In reply to Jakub Jelinek from comment #6)
> Created attachment 40578 [details]
> gcc7-pr77914.patch
>
> So like this (untested)?
Looks good.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79131
--- Comment #2 from Vladimir Makarov ---
(In reply to Vladimir Makarov from comment #1)
>
> Probably the fix will need more time than for pr79058 but I hope to fix it
> on this week.
I have a fix for the PR. Unfortunately it brakes some GCC IP
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71374
--- Comment #4 from Vladimir Makarov ---
(In reply to Jakub Jelinek from comment #3)
>
> ICEs as well with -O1 and above. Vlad, do you think you could have a look?
Sure, I'll look at this when I am done with PR79131.
1 - 100 of 151 matches
Mail list logo