https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83819
Bug 83819 depends on bug 71304, which changed state.
Bug 71304 Summary: missing strlen optimizations after string truncation by
assigning NUL
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71304
What|Removed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71304
Martin Sebor changed:
What|Removed |Added
Status|NEW |RESOLVED
Known to work|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81763
--- Comment #30 from Uroš Bizjak ---
So, I'll bootstrap:
(define_insn "*andndi3_doubleword"
[(set (match_operand:DI 0 "register_operand" "=r,")
(and:DI
(not:DI (match_operand:DI 1 "register_operand" "0,r"))
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84040
nsz at gcc dot gnu.org changed:
What|Removed |Added
CC||aoliva at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81763
Uroš Bizjak changed:
What|Removed |Added
Status|WAITING |NEW
--- Comment #31 from Uroš Bizjak ---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84040
James Greenhalgh changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=37577
--- Comment #7 from Paul Thomas ---
Author: pault
Date: Thu Jan 25 19:09:40 2018
New Revision: 257065
URL: https://gcc.gnu.org/viewcvs?rev=257065=gcc=rev
Log:
2018-25-01 Paul Thomas
PR fortran/37577
*
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83999
--- Comment #5 from paul.richard.thomas at gmail dot com ---
Hi Jakub,
Thanks for the OK and the help in getting the padding sorted out.
Committed as Committed revision 257065.
Paul
On 24 January 2018 at 20:26, Paul Richard Thomas
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81672
--- Comment #2 from David Malcolm ---
Author: dmalcolm
Date: Thu Jan 25 19:19:29 2018
New Revision: 257066
URL: https://gcc.gnu.org/viewcvs?rev=257066=gcc=rev
Log:
jit: remove some unused fields from recording::union_ (PR jit/81672)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83758
Bill Seurer changed:
What|Removed |Added
CC||seurer at linux dot
vnet.ibm.com
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81672
David Malcolm changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81763
--- Comment #32 from Manuel Lauss ---
(In reply to Uroš Bizjak from comment #31)
> (In reply to Uroš Bizjak from comment #30)
> > So, I'll bootstrap:
>
> Maybe we can also allow <- (r,r) for BMI, to be safe (c.f. comment #23):
>
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81763
--- Comment #33 from Jakub Jelinek ---
(In reply to Uroš Bizjak from comment #31)
> (In reply to Uroš Bizjak from comment #30)
> > So, I'll bootstrap:
>
> Maybe we can also allow <- (r,r) for BMI, to be safe (c.f. comment #23):
>
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81763
--- Comment #34 from Uroš Bizjak ---
(In reply to Jakub Jelinek from comment #33)
> At least with a smarter splitter we don't really need to avoid no overlap at
> all for the r <- (r, r) bmi case, we can choose which of the two 32-bit
> andn's
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81763
--- Comment #35 from Jakub Jelinek ---
So, what about following?
--- gcc/config/i386/i386.md.jj 2018-01-16 09:28:19.721432394 +0100
+++ gcc/config/i386/i386.md 2018-01-25 20:58:18.382378827 +0100
@@ -9250,14 +9250,14 @@ (define_split
})
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81763
--- Comment #36 from Jakub Jelinek ---
Ah, bmi, not bmi2. And the =r <- (r, r) alternative might be best first.
--- gcc/config/i386/i386.md.jj 2018-01-16 09:28:19.721432394 +0100
+++ gcc/config/i386/i386.md 2018-01-25 20:58:18.382378827
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81763
--- Comment #37 from Uroš Bizjak ---
(In reply to Jakub Jelinek from comment #33)
> and it should work. The last case would be right now:
> SI:N+1 = SI:N &~ SI:N+2; SI:N+2 = SI:N+1 &~ SI:N+3;
> and is again wrong, but we could again swap:
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81122
Jonathan Wakely changed:
What|Removed |Added
Status|NEW |SUSPENDED
Summary|parsing
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83985
--- Comment #7 from Arnd Bergmann ---
*** Bug 84038 has been marked as a duplicate of this bug. ***
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84038
Arnd Bergmann changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84043
Bug ID: 84043
Summary: -fsanitize=alignment leads to massive compile time
Product: gcc
Version: 7.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84043
--- Comment #1 from Johan Alfredsson ---
Created attachment 43245
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=43245=edit
Preprocessed source
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84043
--- Comment #2 from Johan Alfredsson ---
bash> g++ -v
Using built-in specs.
COLLECT_GCC=/usr/local/products/gcc/7.2.0/bin/g++
COLLECT_LTO_WRAPPER=/usr/local/products/gcc/7.2.0/lib/gcc/x86_64-suse-linux/7.2.0/lto-wrapper
Target: x86_64-suse-linux
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81763
--- Comment #38 from Manuel Lauss ---
(In reply to Jakub Jelinek from comment #36)
Your patch does fix my llvm issue. Thank you!
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83985
Segher Boessenkool changed:
What|Removed |Added
CC||segher at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82518
--- Comment #6 from Christophe Lyon ---
My bisect script cannot find the commit that introduced the problem with
-fno-vect-cost-model, because the build was broken for quite some time.
The regression seems to have been introduced between r197671
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83758
--- Comment #25 from boger at us dot ibm.com ---
A few other variations that enable it to work even with a power8 configuration:
Compiling with -fdisable-ipa-cp prevents the ICE.
OR
Using the //go:nosplit directive before the function
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84044
Bug ID: 84044
Summary: Spurious -Wodr warning with -flto
Product: gcc
Version: 7.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: lto
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83981
--- Comment #8 from Jonathan Wakely ---
I don't think your patch is correct. The whole point of the "move if noexcept"
utilities is that they handle this correctly. If the type is nothrow movable,
then move. Otherwise if it is copyable, then
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84045
Bug ID: 84045
Summary: ICE when is_nothrow_default_constructible is used
before #include
Product: gcc
Version: 7.2.1
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83985
--- Comment #9 from Jakub Jelinek ---
Yes, I do, see #c5. Successfully bootstrapped/regtested (without go which
seems to be broken right now) on powerpc64le-linux and bootstrapped on
powerpc64-linux, will post once regtest (-m64/-m32) on the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83981
--- Comment #9 from Jonathan Wakely ---
Also, if boost::optional had a noexcept move constructor it would work fine.
This is a boost bug.
The part of the patch addressing PR 83982 seems right.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84044
--- Comment #1 from Geoffrey Allott ---
I discovered that in b.cpp a free function
A get() {
return A();
}
also triggers the error. Struct B is not necessary.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83959
Martin Sebor changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84044
--- Comment #2 from Geoffrey Allott ---
Or even simply
A a;
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71501
Martin Sebor changed:
What|Removed |Added
CC||prathamesh3492 at gcc dot
gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83981
--- Comment #10 from Jonathan Wakely ---
(In reply to Jonathan Wakely from comment #8)
> I don't think your patch is correct. The whole point of the "move if
> noexcept" utilities is that they handle this correctly. If the type is
> nothrow
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83981
--- Comment #11 from Daniel Krügler ---
(In reply to Jonathan Wakely from comment #10)
> Perhaps Daniel can comment, since he wrote the resolution of lwg 2033.
>
> Daniel, if the intent was that vector::resize(size_type) must only move,
> even
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83985
--- Comment #10 from Segher Boessenkool ---
Ah, #c6 made me think you wanted to do something else. I didn't look close
enough, sorry. That patch looks good.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84046
Bug ID: 84046
Summary: global zero-sized objects may have same address
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84047
Bug ID: 84047
Summary: missing -Warray-bounds on a negative offset into a
string
Product: gcc
Version: 8.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84047
Martin Sebor changed:
What|Removed |Added
Keywords||diagnostic
Known to work|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=24537
--- Comment #7 from Jonathan Wakely ---
char_traits shouldn't need to be uglified, because it's a reserved name anyway,
due to std::char_traits. That means users can't define macros with that name.
If they get ambiguities due to "using namespace
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83662
--- Comment #5 from Jonathan Wakely ---
Adding this is simple, but I'm worried it will cause issues on Windows, where
detection of that function doesn't seem to work properly (see PR 78565).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56010
Segher Boessenkool changed:
What|Removed |Added
CC||segher at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84047
Martin Sebor changed:
What|Removed |Added
Summary|[6/7/8 Regression] missing |[6/7/8 Regression] missing
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83985
Arnd Bergmann changed:
What|Removed |Added
CC||segher at kernel dot
crashing.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81076
--- Comment #2 from Jonathan Wakely ---
Author: redi
Date: Thu Jan 25 15:24:39 2018
New Revision: 257050
URL: https://gcc.gnu.org/viewcvs?rev=257050=gcc=rev
Log:
PR libstdc++/81076 make __byte_operand SFINAE-friendly
PR libstdc++/81076
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83977
--- Comment #6 from Jakub Jelinek ---
Author: jakub
Date: Thu Jan 25 15:32:02 2018
New Revision: 257051
URL: https://gcc.gnu.org/viewcvs?rev=257051=gcc=rev
Log:
PR middle-end/83977
* ipa-fnsummary.c (compute_fn_summary): Clear
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81076
--- Comment #3 from Jonathan Wakely ---
Author: redi
Date: Thu Jan 25 15:46:46 2018
New Revision: 257055
URL: https://gcc.gnu.org/viewcvs?rev=257055=gcc=rev
Log:
PR libstdc++/81076 make __byte_operand SFINAE-friendly
PR libstdc++/81076
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83830
--- Comment #5 from Jonathan Wakely ---
Author: redi
Date: Thu Jan 25 15:46:41 2018
New Revision: 257054
URL: https://gcc.gnu.org/viewcvs?rev=257054=gcc=rev
Log:
PR libstdc++/83830 Define std::has_unique_object_representations_v
PR
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81076
Jonathan Wakely changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83830
Jonathan Wakely changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83758
--- Comment #23 from acsawdey at gcc dot gnu.org ---
(In reply to Alexandre Oliva from comment #19)
> I was copied, presumably because the problem occurred in var-tracking.
>
> I've tried to duplicate the problem on gcc112. I bootstrapped the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84031
--- Comment #2 from Jakub Jelinek ---
Author: jakub
Date: Thu Jan 25 16:38:40 2018
New Revision: 257057
URL: https://gcc.gnu.org/viewcvs?rev=257057=gcc=rev
Log:
PR c++/84031
* decl.c (find_decomp_class_base): Ignore unnamed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84041
--- Comment #1 from Tom de Vries ---
So, using this patch:
...
diff --git a/gcc/omp-expand.c b/gcc/omp-expand.c
index 90e06310d81..af626d1568a 100644
--- a/gcc/omp-expand.c
+++ b/gcc/omp-expand.c
@@ -167,6 +167,7 @@ is_combined_parallel (struct
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60129
David Malcolm changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81763
Manuel Lauss changed:
What|Removed |Added
CC||manuel.lauss at googlemail dot
com
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83692
--- Comment #6 from Marek Polacek ---
Dang it, hit Save Changes accidentally.
That evaluates the AGGR_INIT_EXPR inside by evaluating the constructor of
outer:
if (m_x.value() != 0) // 1
throw 0;
m_x.m_value = integer{1}.value(); // 2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84038
Arnd Bergmann changed:
What|Removed |Added
Keywords|needs-bisection |
--- Comment #2 from Arnd Bergmann ---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84041
Bug ID: 84041
Summary: [nvptx] Hang in for-3.c
Product: gcc
Version: 8.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libgomp
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84040
Bug ID: 84040
Summary: [8 regression] compilation time of
gcc.c-torture/compile/limits-blockid.c is 50x slower
Product: gcc
Version: 8.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56724
David Malcolm changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84029
--- Comment #2 from Wilco ---
(In reply to Richard Biener from comment #1)
> If we know the length of either argument and the other argument is properly
> aligned we can do a 2, 4 or 8 byte compare upfront. Not sure how often that
> happens
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83985
--- Comment #4 from Jakub Jelinek ---
With a x86_64-linux -> powerpc64-linux cross I can reproduce the hang on
./cc1 -quiet -O2 -m32 pr83985.c -nostdinc -mcpu=e300c3 -mtune=e300c3
but with x86_64-linux -> powerpc-linux cross it ICEs instead:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78809
--- Comment #29 from Wilco ---
(In reply to Qing Zhao from comment #28)
> >
> > I don't think this is a good test. Repeatedly calling strcmp with the same
> > inputs is not something real code does, especially when the string matches
> >
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84033
--- Comment #3 from Alan Modra ---
Author: amodra
Date: Thu Jan 25 23:57:18 2018
New Revision: 257070
URL: https://gcc.gnu.org/viewcvs?rev=257070=gcc=rev
Log:
PR84033, powerpc64le -moptimize-swaps bad code with vec_vbpermq
vbpermq produces its
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84037
Martin Liška changed:
What|Removed |Added
Summary|[8 Regression] Speed|[8 Regression] Speed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83692
--- Comment #5 from Marek Polacek ---
There's a lot that goes on here but the gist is this. In C++17 cp_finish_decl
sees "o" initialized with "{}". check_initializer turns this into
o = TARGET_EXPR
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81860
--- Comment #8 from Gustaw Smolarczyk ---
Hello,
Can I expect the fix to be backported to the gcc 7 branch? gcc 7.3.0 has
apparently shipped with the bug still present.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83692
--- Comment #7 from Marek Polacek ---
So this works but might be too big a hammer. But I have no better ideas.
--- a/gcc/cp/constexpr.c
+++ b/gcc/cp/constexpr.c
@@ -3663,6 +3663,10 @@ cxx_eval_store_expression (const constexpr_ctx *ctx,
tree
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84045
David Malcolm changed:
What|Removed |Added
Keywords||ice-on-valid-code
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83981
--- Comment #12 from Daniel Trebbien ---
https://wg21.link/lwg2158 looks relevant, particularly this part:
"This requirement is not sufficient if an implementation is free to select copy
constructor when !is_nothrow_move_constructible::value &&
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84036
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=14557
nsz at gcc dot gnu.org changed:
What|Removed |Added
CC||nsz at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83990
--- Comment #9 from Jakub Jelinek ---
Another reduced testcase. This one shows the warning with both -O3
-Wnull-dereference -std=c++17 {,-fno-ipa-sra}, but with the former without
location, with the latter with a location.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82718
Mark Wielaard changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83990
--- Comment #10 from Jakub Jelinek ---
namespace b {
typedef long unsigned c;
}
void *operator new(b::c, void *) noexcept;
namespace b {
template < typename d > d *e(d &) noexcept;
template < typename d, d f > struct g { static constexpr d h =
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81611
--- Comment #19 from Georg-Johann Lay ---
Hi, thanks for all that work and efforts.
I tried that patch for the following small test:
extern void foo (void);
extern char volatile vv;
void func2 (const int *p)
{
while (1)
{
int
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84017
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84017
Jakub Jelinek changed:
What|Removed |Added
Priority|P3 |P4
--- Comment #3 from Jakub Jelinek
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81611
--- Comment #20 from Georg-Johann Lay ---
A bit of the bloat reported in PR81625 is also due to missed post-inc
addressing, so it might be worth a look if you are after more test cases.
(Current 8.0.1 perfomrs better than 8.0.0 I used back then:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79704
Bug 79704 depends on bug 81554, which changed state.
Bug 81554 Summary: [8 Regression] 25% performance regression in Himeno benchmark
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81554
What|Removed |Added
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66313
Bug 66313 depends on bug 81554, which changed state.
Bug 81554 Summary: [8 Regression] 25% performance regression in Himeno benchmark
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81554
What|Removed |Added
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81082
Richard Biener changed:
What|Removed |Added
CC||kristerw at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81554
Richard Biener changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84036
Bug ID: 84036
Summary: [8 Regression] ICE on valid code in C++14, variadic
lambda capture in a template function
Product: gcc
Version: 8.0.1
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84037
--- Comment #2 from Martin Liška ---
There's difference of -fopt-info-vec:
$ diff -u /tmp/before /tmp/after
--- /tmp/before 2018-01-25 11:13:03.737658802 +0100
+++ /tmp/after 2018-01-25 11:13:04.737677946 +0100
@@ -1,3 +1,9 @@
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84037
rsandifo at gcc dot gnu.org changed:
What|Removed |Added
CC||rsandifo at gcc dot
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84016
Martin Liška changed:
What|Removed |Added
CC||rsandifo at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82846
Andrey Guskov changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84034
--- Comment #1 from Bernd Edlinger ---
it is acutally a problem with the colorizer:
gcc -fdiagnostics-color=always -Wall -S test.c 2> xx
cat xx
test.c: In function ‘test’:
test.c:5:20: warning: suggest parentheses around ‘&&’ within ‘||’
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84036
Richard Biener changed:
What|Removed |Added
Keywords||ice-on-valid-code
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84037
Richard Biener changed:
What|Removed |Added
Priority|P3 |P1
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84037
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83990
--- Comment #8 from Jakub Jelinek ---
(In reply to Martin Jambor from comment #7)
> (In reply to Jakub Jelinek from comment #4)
> >
> > ...
> >
> > The statement on which on the original testcase it warns indeed has no
> > location, that was
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84003
--- Comment #4 from Richard Biener ---
Looks like we eventually need sth like
/* If the later store we delete could have changed the
dynamic type of the memory make sure the one we
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84031
Jakub Jelinek changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84028
--- Comment #2 from Tom de Vries ---
Author: vries
Date: Thu Jan 25 10:25:14 2018
New Revision: 257046
URL: https://gcc.gnu.org/viewcvs?rev=257046=gcc=rev
Log:
[nvptx, PR84028] Add exit insn after noreturn call for neutered workers
2018-01-25
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84003
Richard Biener changed:
What|Removed |Added
Status|NEW |ASSIGNED
CC|
201 - 300 of 330 matches
Mail list logo