Hi!
The following patch adds folding for vector shift by scalar builtins.
If they are masked, so far we only optimize them only if the mask is all
ones. ix86_fold_builtin handles the all constant argument cases, where the
effect of the instructions can be fully precomputed at compile time and
On 07/05/18 22:20 +0200, François Dumont wrote:
Hi
Here is the patch to add backtrace info to debug assertion failure
output.
Example:
/home/fdt/dev/gcc/build/x86_64-pc-linux-gnu/libstdc++-v3/include/debug/vector:188:
In function:
std::__debug::vector<_Tp,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85695
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
Hi!
Since r247992 the cmpelim pass optimizes a few arithmetics with following
comparisons and some of the peephole2s we have to recognize RMW instructions
with comparisons don't trigger anymore.
In particular, on the pr49095.c testcase in GCC 7 only 8 functions used
load + comparison with arith +
Hi,
this patch prevents lto-option to store some flags that does not make snese to
store,
in partiuclar dumpdir and -fresolution. These definitly should not be preserved
from
compile time to link time and in case of incremental linking they caused
trouble with
wrong resolution file being used
On 8 May 2018 at 15:45, Marc Glisse wrote:
> On Tue, 8 May 2018, Jonathan Wakely wrote:
>
>> On 8 May 2018 at 14:00, Jonathan Wakely wrote:
>>>
>>> On 8 May 2018 at 13:44, Stephan Bergmann wrote:
I was recently bitten by the following issue (Linux, libstdc++
Hi,
this patch makes lto-wrapper to look for -flinker-output=rel and in this
case confiugre lto1 in non-WHOPR mode + disable section renaming.
Bootstrapped/regtested x86_64-linux with rest of incremental link patchset.
OK?
* lto-wrapper.c (debug_objcopy): Add rename parameter; pass
Hi!
While working on PR85323 testsuite coverage, I've noticed we lack these
intrinsics. ICC and since Mar 2017 also clang do have these.
The _mm512_setzero is just a misnamed alias to another intrinsic, but for
compatibility we likely want to have it too.
Surprisingly, the
Hi,
with lto, incremental linking can be meaninfuly done in three ways:
1) read LTO file and produce non-LTO .o file
this is current behaviour of gcc -r or ld -r with plugin
2) read LTO files and merge section for later LTO
this is current behaviour of ld -r w/o plugin
3) read LTO files
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85699
Bug ID: 85699
Summary: [8 regression] gcc.dg/nextafter-2.c fail
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
Hi,
for incremental linking of LTO objects we need to copy debug sections from
source object files into destination without renaming them from .gnu.debuglto
into the standard debug section (because they will again be LTO debug section
in the resulting object file).
I have discussed this with
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85698
Bug ID: 85698
Summary: CPU2017 525.x264_r fails starting with r257581
Product: gcc
Version: 8.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85697
Bug ID: 85697
Summary: At -Os nontrivial ctor does not use SSE to zero
Product: gcc
Version: 8.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85103
David Edelsohn changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85692
--- Comment #5 from Allan Jensen ---
Created attachment 44088
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44088=edit
suggested patch
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85692
--- Comment #4 from Allan Jensen ---
Note I already posted a patch on gcc-patches myself. It is very similar to
yours
On Tue, 8 May 2018, Jonathan Wakely wrote:
On 8 May 2018 at 14:00, Jonathan Wakely wrote:
On 8 May 2018 at 13:44, Stephan Bergmann wrote:
I was recently bitten by the following issue (Linux, libstdc++ 8.0.1): A
process loads two dynamic libraries A and B both using std::regex, and A is
Hi,
On 20/04/2018 19:46, Paolo Carlini wrote:
Hi,
in this error-recovery regression, after sensible diagnostic about
"two or more data types in declaration..." we get confused, we issue a
cryptic - but useful hint to somebody working on the present bug ;) -
"template definition of
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85694
--- Comment #2 from Richard Biener ---
Hmm, but if you have 255 + 255 + 1 then you need to use pavgw at least,
otherwise the vectorization isn't semantically equivalent? Or do the
instructions compute
the intermediate results in greater
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85694
Richard Biener changed:
What|Removed |Added
Keywords||missed-optimization
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85696
--- Comment #2 from gcc-bugzilla at zulan dot net ---
Created attachment 44087
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44087=edit
minimal example
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85696
gcc-bugzilla at zulan dot net changed:
What|Removed |Added
Attachment #44085|0 |1
is obsolete|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85696
Bug ID: 85696
Summary: OpenMP with variably modified and default(none) won't
compile
Product: gcc
Version: 8.1.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85634
Jason Merrill changed:
What|Removed |Added
CC||jason at gcc dot gnu.org
--- Comment #6
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85693
Uroš Bizjak changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85692
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #3
Hi Luis,
On 07/05/18 15:28, Luis Machado wrote:
Hi,
On 02/08/2018 10:45 AM, Luis Machado wrote:
Hi Kyrill,
On 02/08/2018 09:48 AM, Kyrill Tkachov wrote:
Hi Luis,
On 06/02/18 15:04, Luis Machado wrote:
Thanks for the feedback Kyrill. I've adjusted the v2 patch based on your
suggestions and
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85695
Bug ID: 85695
Summary: if constexpr misevaluates typedefed type value
Product: gcc
Version: 8.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85694
Bug ID: 85694
Summary: Generation of vectorized AVG (Average) instruction
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85693
Richard Biener changed:
What|Removed |Added
CC||rguenth at gcc dot gnu.org
--- Comment
On Tue, May 8, 2018 at 3:25 PM, Richard Sandiford
wrote:
> We build up the input to IFN_STORE_LANES one vector at a time.
> In RTL, each of these vector assignments becomes a write to
> subregs of the form (subreg:VEC (reg:AGGR R)), where R is the
> eventual input to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85693
Bug ID: 85693
Summary: Generation of SAD (Sum of Absolute Difference)
instruction
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
On 08/05/18 12:43, Richard Sandiford wrote:
Move the C++ tests that were originally in gcc.target/aarch64/sve
and later g++.dg/other to g++.target/aarch64/sve. This means that
we don't need to override the -march flag when testing with something
that already supports SVE.
Tested on
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85672
Jonathan Wakely changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85616
Denis Roux changed:
What|Removed |Added
Resolution|INVALID |FIXED
--- Comment #6 from Denis Roux ---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85615
Richard Biener changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85597
--- Comment #5 from Richard Biener ---
Author: rguenth
Date: Tue May 8 13:33:54 2018
New Revision: 260044
URL: https://gcc.gnu.org/viewcvs?rev=260044=gcc=rev
Log:
2018-05-08 Richard Biener
Backport from mainline
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85615
--- Comment #8 from Richard Biener ---
Author: rguenth
Date: Tue May 8 13:33:54 2018
New Revision: 260044
URL: https://gcc.gnu.org/viewcvs?rev=260044=gcc=rev
Log:
2018-05-08 Richard Biener
Backport from mainline
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85588
--- Comment #10 from Richard Biener ---
Author: rguenth
Date: Tue May 8 13:33:54 2018
New Revision: 260044
URL: https://gcc.gnu.org/viewcvs?rev=260044=gcc=rev
Log:
2018-05-08 Richard Biener
Backport from mainline
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85567
--- Comment #4 from Richard Biener ---
Author: rguenth
Date: Tue May 8 13:33:54 2018
New Revision: 260044
URL: https://gcc.gnu.org/viewcvs?rev=260044=gcc=rev
Log:
2018-05-08 Richard Biener
Backport from mainline
We build up the input to IFN_STORE_LANES one vector at a time.
In RTL, each of these vector assignments becomes a write to
subregs of the form (subreg:VEC (reg:AGGR R)), where R is the
eventual input to the store lanes instruction. The problem is
that RTL isn't very good at tracking liveness when
Here is a patch to teach _Parameter type about special iterator types so
that it improves final output.
It also get rid of the debug layer when possible so that failure output
is cleaner. Debug mode is already transparent to users there is no need
to show the Debug types in the output.
Here
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85672
--- Comment #13 from Jonathan Wakely ---
Author: redi
Date: Tue May 8 13:05:04 2018
New Revision: 260043
URL: https://gcc.gnu.org/viewcvs?rev=260043=gcc=rev
Log:
PR libstdc++/85672 #undef _GLIBCXX_USE_FLOAT128 when not supported
Restore the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61502
--- Comment #29 from Peter Sewell ---
On 8 May 2018 at 08:22, rguenth at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61502
>
> --- Comment #25 from Richard Biener ---
> (In reply to Harald
On 8 May 2018 at 14:00, Jonathan Wakely wrote:
> On 8 May 2018 at 13:44, Stephan Bergmann wrote:
>> I was recently bitten by the following issue (Linux, libstdc++ 8.0.1): A
>> process loads two dynamic libraries A and B both using std::regex, and A is
>> compiled without -D_GLIBCXX_DEBUG while B
The one for the prologue mflr did not have any value set, which means
use the SET that is in the insn pattern. This works fine, except when
some late pass decides to replace the SET_SRC -- this changes the
meaning of the REG_CFA_REGISTER! Such passes should not do these
things, but let's be more
On 8 May 2018 at 13:44, Stephan Bergmann wrote:
> I was recently bitten by the following issue (Linux, libstdc++ 8.0.1): A
> process loads two dynamic libraries A and B both using std::regex, and A is
> compiled without -D_GLIBCXX_DEBUG while B is compiled with -D_GLIBCXX_DEBUG.
This is only
In the testcase for PR85645 we do a pretty dumb placement of the
prologue/epilogue for the LR component: we place an epilogue for LR
before a control flow split where one of the branches clobbers LR
eventually, and the other does not. The branch that does clobber it
will need a prologue again
We should never change the destination of a REG_CFA_REGISTER, just
like for insns with a REG_CFA_RESTORE, because we need to have the
same control flow information on all branches that join. It is very
doubtful that renaming the scratch registers used for prologue/epilogue
will help anything
I was recently bitten by the following issue (Linux, libstdc++ 8.0.1):
A process loads two dynamic libraries A and B both using std::regex, and
A is compiled without -D_GLIBCXX_DEBUG while B is compiled with
-D_GLIBCXX_DEBUG. B creates an instance of std::regex, which internally
creates a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85572
Jakub Jelinek changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85480
Jakub Jelinek changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85317
Jakub Jelinek changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85572
--- Comment #3 from Jakub Jelinek ---
Author: jakub
Date: Tue May 8 12:16:19 2018
New Revision: 260041
URL: https://gcc.gnu.org/viewcvs?rev=260041=gcc=rev
Log:
PR target/85572
* config/i386/i386.c (ix86_expand_sse2_abs): Handle
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85317
--- Comment #2 from Jakub Jelinek ---
Author: jakub
Date: Tue May 8 12:04:25 2018
New Revision: 260040
URL: https://gcc.gnu.org/viewcvs?rev=260040=gcc=rev
Log:
PR target/85317
* config/i386/i386.c (ix86_fold_builtin): Handle
On Mai 08 2018, Florian Weimer wrote:
> I wonder if it's currently a warning because the implicit int is used in
> configure checks.
Is it? At least in the GCC sources I couldn't find any occurence of
main without a preceding int.
Andreas.
--
Andreas Schwab, SUSE Labs,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85480
--- Comment #2 from Jakub Jelinek ---
Author: jakub
Date: Tue May 8 12:02:38 2018
New Revision: 260039
URL: https://gcc.gnu.org/viewcvs?rev=260039=gcc=rev
Log:
PR target/85480
* config/i386/sse.md (ssequaterinsnmode): New mode
In this testcase shrink-wrap makes a not-so-great decision. Both regcprop
and regrename cannot handle the resulting RTL correctly. The first two
patches fix those passes.
The third patch makes separate shrink-wrapping do a better job: running
spread_components more than once should help only in
Changing a SET that has a REG_CFA_REGISTER note is wrong if we are
changing the SET_DEST, or if the REG_CFA_REGISTER has nil as its
argument, and maybe some other cases. It's never really useful to
propagate into such an instruction, so let's just bail whenever we
see such a note.
Bootstrapped
Sorry, forgot attachment.
Sebastian
-Original Message-
From: Peryt, Sebastian
Sent: Tuesday, May 8, 2018 1:56 PM
To: gcc-patches@gcc.gnu.org
Cc: Uros Bizjak ; Kirill Yukhin ;
Peryt, Sebastian
Subject:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85682
--- Comment #2 from Luis Machado ---
Did it even bootstrap properly? It shouldn't have been built in the first place
i guess, due to the signedness error of a particular chunk of code.
I did a fresh x86-64 bootstrap with the changes in and
Hi,
This patch adds support for CLDEMOTE instruction.
Is it ok for trunk and after few day for backport to GCC-8?
2018-05-08 Sebastian Peryt
gcc/
* common/config/i386/i386-common.c (OPTION_MASK_ISA_CLDEMOTE_SET,
OPTION_MASK_ISA_CLDEMOTE_UNSET):
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85692
Richard Biener changed:
What|Removed |Added
Keywords||missed-optimization
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85665
--- Comment #7 from Jonathan Wakely ---
(In reply to Richard Biener from comment #5)
> Guessing this might be arm...
Maybe some of them are arm but some are in other targets.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85665
--- Comment #6 from Jonathan Wakely ---
(In reply to Roland Illig from comment #3)
> (In reply to Jonathan Wakely from comment #2)
> > It might be better to report multiple bugs, one per target backend, so that
> > the relevant target
Move the C++ tests that were originally in gcc.target/aarch64/sve
and later g++.dg/other to g++.target/aarch64/sve. This means that
we don't need to override the -march flag when testing with something
that already supports SVE.
Tested on aarch64-linux-gnu (with and without SVE) and
On 8 May 2018 at 12:35, Florian Weimer wrote:
> On 04/25/2018 04:40 PM, Jonathan Wakely wrote:
>>
>> More concretely, deprecating it for a few releases would allow us to
>> apply the attached patch at some point in the future, so that instead
>> of:
>>
>> rt.c:1:6: warning: ISO C++ forbids
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85654
rsandifo at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
On 04/25/2018 04:40 PM, Jonathan Wakely wrote:
More concretely, deprecating it for a few releases would allow us to
apply the attached patch at some point in the future, so that instead
of:
rt.c:1:6: warning: ISO C++ forbids declaration of ‘main’ with no type
[-Wreturn-type]
main() { return
Hi,
This patch adds support for WAITPKG instructions.
Is it ok for trunk and after few day for backport to GCC-8?
2018-05-08 Sebastian Peryt
gcc/
* common/config/i386/i386-common.c (OPTION_MASK_ISA_WAITPKG_SET,
OPTION_MASK_ISA_WAITPKG_UNSET): New
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=19808
--- Comment #37 from Jonathan Wakely ---
N.B. we should also warn using uninitialized members in default member
initializers, e.g. both of these should produce a warning:
struct X {
int x1 = x2;
int x2 = 0;
};
X x{}; // causes definition
On Dienstag, 8. Mai 2018 12:42:33 CEST Richard Biener wrote:
> On Tue, May 8, 2018 at 12:37 PM, Allan Sandfeld Jensen
>
> wrote:
> > I have tried to fix PR85692 that I opened.
>
> Please add a testcase as well. It also helps if you shortly tell what
> the patch does
> in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85691
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=19808
Jonathan Wakely changed:
What|Removed |Added
CC||roger at rankedgaming dot com
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85654
--- Comment #2 from rsandifo at gcc dot gnu.org
---
(In reply to Richard Biener from comment #1)
> Not sure why we don't use versioning for alignment here.
I think it's probably a case of not knowing at that stage that
out[] is going to be
Hello Jakub!
On 23 апр 20:31, Jakub Jelinek wrote:
> Hi!
>
> As mentioned in the PR, vmov{aps,apd,dqa{,32,64}} 128-bit instructions
> zero the rest of 512-bit register, so we can optimize insertion into zero
> vectors using those instructions.
>
> Bootstrapped/regtested on x86_64-linux and
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85586
--- Comment #9 from rsandifo at gcc dot gnu.org
---
Author: rsandifo
Date: Tue May 8 11:18:40 2018
New Revision: 260037
URL: https://gcc.gnu.org/viewcvs?rev=260037=gcc=rev
Log:
Tighten condition in vect/pr85586.c (PR 85654)
2018-05-08
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85586
--- Comment #8 from rsandifo at gcc dot gnu.org
---
Author: rsandifo
Date: Tue May 8 11:17:57 2018
New Revision: 260036
URL: https://gcc.gnu.org/viewcvs?rev=260036=gcc=rev
Log:
Tighten condition in vect/pr85586.c (PR 85654)
2018-05-08
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85690
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85672
--- Comment #12 from Jonathan Wakely ---
Thanks for the suggestion, it would clean up a few things in c++config so I'll
move to that next time, instead of adding another hack.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85672
--- Comment #11 from Marc Glisse ---
(In reply to Jonathan Wakely from comment #8)
> My autotools-fu is too weak to come up with anything better but I'd be very
> happy if you can suggest something cleaner.
For the general case, the autoconf
Hi,
On 08/05/2018 01:02, Nathan Sidwell wrote:
As prophesied by gcc 8.1, I have nuked the ARM-era for-scope
compatibilty of -fno-for-scope. It has been a c++98-only feature, and
that's not the default anymore. Time for this to go.
Nice. I'm sure that for a while we had a bug in Bugzilla due
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85689
Richard Biener changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
Hello Jakub!
On 07 мая 10:20, Jakub Jelinek wrote:
> Hi!
>
> The following patch handles constant folding of the builtins used in
> *movemask* intrinsics - they have single operand and the only useful folding
> seems to be if the argument is VECTOR_CST, we can do what the instruction
> would do
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57429
Paolo Carlini changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57429
--- Comment #2 from paolo at gcc dot gnu.org ---
Author: paolo
Date: Tue May 8 10:47:24 2018
New Revision: 260035
URL: https://gcc.gnu.org/viewcvs?rev=260035=gcc=rev
Log:
2018-05-08 Paolo Carlini
PR
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85669
--- Comment #4 from Douglas Mencken ---
(In reply to Richard Biener from comment #3)
> How did you configure?
As always
../gcc-8.1.0/configure \
--build=powerpc-unknown-darwin --host=powerpc-unknown-darwin
--target=powerpc-unknown-darwin \
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85683
Richard Biener changed:
What|Removed |Added
Priority|P3 |P2
On Tue, May 8, 2018 at 12:37 PM, Allan Sandfeld Jensen
wrote:
> I have tried to fix PR85692 that I opened.
Please add a testcase as well. It also helps if you shortly tell what
the patch does
in your mail.
Thanks,
Richard.
> 2018-05-08 Allan Sandfeld Jense
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85680
Richard Biener changed:
What|Removed |Added
Keywords||missed-optimization
On 1 May 2018 at 05:05, Sameera Deshpande wrote:
> On 13 April 2018 at 20:21, James Greenhalgh wrote:
>> On Fri, Apr 13, 2018 at 03:39:32PM +0100, Sameera Deshpande wrote:
>>> On Fri 13 Apr, 2018, 8:04 PM James Greenhalgh,
>>>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85658
Richard Earnshaw changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
I have tried to fix PR85692 that I opened.
2018-05-08 Allan Sandfeld Jense
PR tree-optimization/85692
* tree-ssa-forwprop.c (simplify_vector_constructor): Detect
two source permute operations as well.
diff --git a/gcc/tree-ssa-forwprop.c
There are a number of places in parsecpu.awk where I've managed to get
the operator precedence between ! and 'in' incorrect (! binds more
tightly). In most cases this just makes a consistency test ineffective,
but in a few cases it means we fail to correctly diagnose errors by the
user (for
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85658
--- Comment #6 from Richard Earnshaw ---
Author: rearnsha
Date: Tue May 8 10:33:33 2018
New Revision: 260034
URL: https://gcc.gnu.org/viewcvs?rev=260034=gcc=rev
Log:
[arm] PR target/85658 Fix operator precedence errors in parsecpu.awk
There
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85678
Richard Biener changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85680
--- Comment #4 from Marc Glisse ---
All memset come from ldist, so already quite late in the pipeline. Maybe
clang/intel, who avoid a comparison between new and the first memset, generate
memset directly from the front-end? (clang generates the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85669
Richard Biener changed:
What|Removed |Added
Keywords||build
Component|regression
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85666
Wilco changed:
What|Removed |Added
CC||wilco at gcc dot gnu.org
--- Comment #3 from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85658
--- Comment #5 from Richard Earnshaw ---
Author: rearnsha
Date: Tue May 8 10:21:34 2018
New Revision: 260032
URL: https://gcc.gnu.org/viewcvs?rev=260032=gcc=rev
Log:
[arm] PR target/85658 Fix operator precedence errors in parsecpu.awk
There
101 - 200 of 247 matches
Mail list logo