On Thu, 2020-02-13 at 22:18 +, Modi Mo wrote:
> > On 2/12/20 8:53 PM, David Malcolm wrote:
> > > Thanks for the patch.
> > >
> > > Some nitpicks:
> > >
> > > Timing-wise, the GCC developer community is focusing on gcc 10
> > > bugfixing right now (aka "stage 4" of the release cycle). So
Snapshot gcc-9-20200215 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/9-20200215/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 9 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93720
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
This avoids instantiating dead code when the true branch of the constexpr if is
taken.
[ diffstat generated with -w to ignore noisy whitespace changes ]
libstdc++-v3/ChangeLog:
* include/bits/ranges_algo.h (__lexicographical_compare_fn::operator()):
Move code after an early exit
On 2/13/20 12:42 AM, Jason Merrill wrote:
While partially instantiating a generic lambda, we can encounter pack
expansions or constexpr if where we can't actually do the substitution
immediately, and instead remember a partial instantiation context
in *_EXTRA_ARGS. This includes any
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92583
--- Comment #5 from CVS Commits ---
The master branch has been updated by Jason Merrill :
https://gcc.gnu.org/g:d71365427670a791c5b54bfec6e3d41210844a8a
commit r10-6648-gd71365427670a791c5b54bfec6e3d41210844a8a
Author: Jason Merrill
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90764
--- Comment #5 from CVS Commits ---
The master branch has been updated by Jason Merrill :
https://gcc.gnu.org/g:4d5bb56b1d3e6873a7d08dc8f5f4a4997e51bfde
commit r10-6647-g4d5bb56b1d3e6873a7d08dc8f5f4a4997e51bfde
Author: Jason Merrill
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #182 from dave.anglin at bell dot net ---
On 2020-02-14 11:04 p.m., peter.bisroev at groundlabs dot com wrote:
> However just below this check, configure looks for GNU linker, and if one not
> found, disables COMDAT group support even
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68061
--- Comment #4 from CVS Commits ---
The master branch has been updated by Jason Merrill :
https://gcc.gnu.org/g:acff02ef1f4bc951ab7b4e3fdc117e0646d5d8f5
commit r10-6650-gacff02ef1f4bc951ab7b4e3fdc117e0646d5d8f5
Author: Jason Merrill
Date:
On x86, when AVX and AVX512 are enabled, vector move instructions can
be encoded with either 2-byte/3-byte VEX (AVX) or 4-byte EVEX (AVX512):
0: c5 f9 6f d1 vmovdqa %xmm1,%xmm2
4: 62 f1 fd 08 6f d1 vmovdqa64 %xmm1,%xmm2
We prefer VEX encoding over EVEX since VEX is
There is no need to set mode attribute to XImode nor V8DFmode since
ix86_output_ssemov can properly encode xmm16-xmm31 registers with and
without AVX512VL.
gcc/
PR target/89229
* config/i386/i386.md (*movdf_internal): Call ix86_output_ssemov
for TYPE_SSEMOV. Remove
There is no need to set mode attribute to XImode since ix86_output_ssemov
can properly encode xmm16-xmm31 registers with and without AVX512VL.
gcc/
PR target/89229
* config/i386/i386.md (*movsi_internal): Call ix86_output_ssemov
for TYPE_SSEMOV. Remove
There is no need to set mode attribute to XImode since ix86_output_ssemov
can properly encode ymm16-ymm31 registers with and without AVX512VL.
PR target/89229
* config/i386/i386.md (*movoi_internal_avx): Call
ix86_output_ssemov for TYPE_SSEMOV. Remove ext_sse_reg_operand
This patch set was originally submitted in Feb 2019:
https://gcc.gnu.org/ml/gcc-patches/2019-02/msg01841.html
I broke it into 10 smaller patches for easy review.
On x86, when AVX and AVX512 are enabled, vector move instructions can
be encoded with either 2-byte/3-byte VEX (AVX) or 4-byte EVEX
There is no need to set mode attribute to XImode since ix86_output_ssemov
can properly encode xmm16-xmm31 registers with and without AVX512VL.
gcc/
PR target/89229
* config/i386/i386.md (*movti_internal): Call ix86_output_ssemov
for TYPE_SSEMOV. Remove
There is no need to set mode attribute to XImode since ix86_output_ssemov
can properly encode xmm16-xmm31 registers with and without AVX512VL.
gcc/
PR target/89229
* config/i386/i386.md (*movdi_internal): Call ix86_output_ssemov
for TYPE_SSEMOV. Remove
PR target/89229
* config/i386/i386.md (*movxi_internal_avx512f): Call
ix86_output_ssemov for TYPE_SSEMOV.
---
gcc/config/i386/i386.md | 6 +-
1 file changed, 1 insertion(+), 5 deletions(-)
diff --git a/gcc/config/i386/i386.md b/gcc/config/i386/i386.md
index
There is no need to set mode attribute to V16SFmode since ix86_output_ssemov
can properly encode xmm16-xmm31 registers with and without AVX512VL.
gcc/
PR target/89229
* config/i386/i386.md (*movdf_internal): Call ix86_output_ssemov
for TYPE_SSEMOV. Remove
There is no need to set mode attribute to XImode since ix86_output_ssemov
can properly encode xmm16-xmm31 registers with and without AVX512VL.
Remove ext_sse_reg_operand since it is no longer needed.
PR target/89229
* config/i386/mmx.md (MMXMODE:*mov_internal): Call
gcc/
PR target/89229
* config/i386/i386.md (*movtf_internal): Call ix86_output_ssemov
for TYPE_SSEMOV.
gcc/testsuite/
PR target/89229
* gcc.target/i386/pr89229-5a.c: New test.
* gcc.target/i386/pr89229-5b.c: Likewise.
*
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #183 from dave.anglin at bell dot net ---
On 2020-02-15 12:49 a.m., peter.bisroev at groundlabs dot com wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
>
> --- Comment #180 from Peter Bisroev ---
> (In reply to
find_template_parameters needs to find the mention of T in the lambda.
Fixing that leaves this as a hard error, which may be surprising but is
consistent with lambdas in other SFINAE contexts like template argument
deduction.
Tested x86_64-pc-linux-gnu, applying to trunk.
gcc/cp/ChangeLog
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92556
--- Comment #2 from CVS Commits ---
The master branch has been updated by Jason Merrill :
https://gcc.gnu.org/g:1e166191ef330f3491d405bf3eb09b2b796c9b0e
commit r10-6649-g1e166191ef330f3491d405bf3eb09b2b796c9b0e
Author: Jason Merrill
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #184 from dave.anglin at bell dot net ---
On 2020-02-15 12:56 a.m., peter.bisroev at groundlabs dot com wrote:
> So we made some progress here. I have rebuilt 4.7.4 with --enable-comdat. 3
> stage bootstrap went fine (running 'make
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54367
Bug 54367 depends on bug 92556, which changed state.
Bug 92556 Summary: [10 Regression] ICE if using dependent name inside lambda
expression in simple-requirement since r10-3735-gcb57504a55015891
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92556
Jason Merrill changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
On Sat, 15 Feb 2020, Jonathan Wakely wrote:
> On 14/02/20 10:35 -0500, Patrick Palka wrote:
> > These subroutines have only a single call site, so it might be best and
> > simplest
> > to eliminate them before we convert the algos into function objects.
> >
> > libstdc++-v3/ChangeLog:
> >
> >
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93759
Bug ID: 93759
Summary: Invalid % in param
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: translation
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93760
--- Comment #1 from Andrew Pinski ---
Should be "while the other does not"
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93744
--- Comment #7 from CVS Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:187dd955dbee3939c3a2ca7b6839e7f70125
commit r10-6646-g187dd955dbee3939c3a2ca7b6839e7f70125
Author: Jakub Jelinek
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93744
--- Comment #8 from Jakub Jelinek ---
As for the signed zeros, I can't really reproduce it. Tried with:
__attribute__((noipa)) void
foo (int x)
{
double a = 0.0;
double b = -0.0;
_Bool c = x > 0;
_Bool d = x > 1;
double e = c;
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93744
--- Comment #9 from CVS Commits ---
The releases/gcc-9 branch has been updated by Jakub Jelinek
:
https://gcc.gnu.org/g:498055331393d3c32fea5a6142c926b6a7700b8d
commit r9-8241-g498055331393d3c32fea5a6142c926b6a7700b8d
Author: Jakub Jelinek
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93565
--- Comment #23 from Andreas Schwab ---
gcc.target/aarch64/pr93565.c fails with -mabi=ilp32.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93755
Bug ID: 93755
Summary: nested quotes in command line options errors
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93756
Bug ID: 93756
Summary: typo: compatable
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: other
Assignee:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93758
Bug ID: 93758
Summary: Building x86_64-w64-mingw32-gcc (mingw-w64) on macOS
Catalina results in "internal compiler error:
Segmentation fault"
Product: gcc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93743
Uroš Bizjak changed:
What|Removed |Added
Status|NEW |ASSIGNED
CC|uros at gcc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93756
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93760
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
On February 15, 2020 7:09:51 AM GMT+01:00, Jakub Jelinek
wrote:
>Hi!
>
>As the following testcases show (the first one reported, last two
>found by code inspection), we need to disallow side-effects
>in simplifications that turn some unconditional expression into
>conditional
>one. From my
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78756
Mojca Miklavec changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93747
Roland Illig changed:
What|Removed |Added
Status|RESOLVED|UNCONFIRMED
Resolution|INVALID
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93749
--- Comment #3 from Roland Illig ---
Even though the GCC warnings are suppressed, these strings still show up in the
translatable strings. In the German translation I'm just copying them 1:1,
since that makes sense to me.
I still don't
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93760
Bug ID: 93760
Summary: wrong grammar in diagnostic
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: ipa
* include/bits/random.h (uniform_random_bit_generator): Require min()
and max() to be constant expressions and min() to be less than max().
* testsuite/26_numerics/random/concept.cc: Check additional cases.
* testsuite/26_numerics/random/pr60037-neg.cc: Adjust
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93589
Jason Merrill changed:
What|Removed |Added
CC||jason at gcc dot gnu.org
--- Comment #7
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93757
Bug ID: 93757
Summary: [GCOV] incorrect coverage for inline function with
"a?b:c" expression
Product: gcc
Version: 9.2.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93759
--- Comment #1 from Andreas Schwab ---
Apparently the problem is that "% p" looks like a valid c-format.
Now that this feature has been approved for C++20 we can define the
macro to the official value.
* include/bits/erase_if.h (__cpp_lib_erase_if): Define to 202002L.
* include/std/deque: Likewise.
* include/std/forward_list: Likewise.
* include/std/list: Likewise.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93744
Jakub Jelinek changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93744
--- Comment #10 from CVS Commits ---
The releases/gcc-8 branch has been updated by Jakub Jelinek
:
https://gcc.gnu.org/g:e24c48585721fc4122ae10282e32af49aff4c380
commit r8-10025-ge24c48585721fc4122ae10282e32af49aff4c380
Author: Jakub Jelinek
This libgo patch limits the default value of GOMAXPROCS to 32 on
32-bit systems. Otherwise we can easily run out of stack space for
threads. The user can still override by setting GOMAXPROCS.
Bootstrapped and ran Go testsuite on x86_64-pc-linux-gnu. Committed
to mainline.
Ian
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93761
Bug ID: 93761
Summary: ICE when compiling a standard header as a header unit
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93761
--- Comment #1 from Christopher Di Bella ---
Created attachment 47846
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47846=edit
Iterator temp
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93741
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
I've committed a patch to update libgo to the 1.14rc1 release (this is
a release candidate for the 1.14 Go release). Bootstrapped and ran Go
testsuite on x86_64-pc-linux-gnu. Committed to mainline.
Ian
patch.txt.bz2
Description: application/bzip
‐‐‐ Original Message ‐‐‐
On Friday, February 14, 2020 6:46 PM, Segher Boessenkool
wrote:
> On Fri, Feb 14, 2020 at 08:24:30PM +, GT wrote:
>
> > Function rs6000_simd_clone_adjust, even though it's body is empty,
> > cannot simply be removed. I tried it. It resulted in ICE. In my
> >
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93759
--- Comment #2 from Roland Illig ---
(In reply to Andreas Schwab from comment #1)
> Apparently the problem is that "% p" looks like a valid c-format.
Then there's a bug in either gettext or the GCC definitions of where c-format
strings may
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #185 from Peter Bisroev ---
(In reply to dave.anglin from comment #184)
> On 2020-02-15 12:56 a.m., peter.bisroev at groundlabs dot com wrote:
> > So we made some progress here. I have rebuilt 4.7.4 with --enable-comdat. 3
> > stage
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #187 from Peter Bisroev ---
(In reply to dave.anglin from comment #183)
> On 2020-02-15 12:49 a.m., peter.bisroev at groundlabs dot com wrote:
> > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
> >
> > --- Comment #180 from Peter
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91847
--- Comment #2 from Barry Revzin ---
In the Prague meeting, this paper
(https://brevzin.github.io/cpp_proposals/2095_lambda_pack_cwg/p2095r0.html) was
adopted into what will become the C++20 standard, which moves the & in the
grammar to the left
On 15/02/20 11:28 -0500, Patrick Palka wrote:
This avoids instantiating dead code when the true branch of the constexpr if is
taken.
[ diffstat generated with -w to ignore noisy whitespace changes ]
libstdc++-v3/ChangeLog:
* include/bits/ranges_algo.h
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #186 from Peter Bisroev ---
Created attachment 47847
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47847=edit
Basic compiler tests v00
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93762
Bug ID: 93762
Summary: Truncation of deferred-length string when passing as
optional
Product: gcc
Version: 8.2.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93763
Andrew Pinski changed:
What|Removed |Added
Keywords||ice-on-valid-code
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93753
Andrew Pinski changed:
What|Removed |Added
Keywords||ice-on-invalid-code
--- Comment #1 from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93758
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
This libbacktrace patch updates the test file used for comparisons
with zlib. The file that the test was previously using, from libgo,
no longer exists. Use its replacement file instead. Bootstrapped and
ran libbacktrace tests on x86_64-pc-linux-gnu. Committed to mainline.
Ian
2020-02-15
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93710
Marek Polacek changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93710
Marek Polacek changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93710
--- Comment #5 from CVS Commits ---
The master branch has been updated by Marek Polacek :
https://gcc.gnu.org/g:eef65c474e6836cc0470eb84f28895050161fcb8
commit r10-6657-geef65c474e6836cc0470eb84f28895050161fcb8
Author: Marek Polacek
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93764
Andrew Pinski changed:
What|Removed |Added
Keywords||wrong-code
Component|c
It's probably past time for this, but definitely now that we're done with
the final committee meeting of C++20. This patch only adds the option and
adjusts the testsuite to recognize it; more extensive changes can wait for
the published standard.
Tested x86_64-pc-linux-gnu, applying to trunk.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93763
Bug ID: 93763
Summary: ice in propagate_vals_across_arith_jfunc, at
ipa-cp.c:2039
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93764
Bug ID: 93764
Summary: lzo 2.10 test suite fails with -O2 and -O3
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93751
--- Comment #3 from Alexey Neyman ---
Well, why not fix it then? :) It should be a fairly low risk change, since it
does not remove any DIEs - I think it is quite unlikely that any user depends
on the *absence* of DIEs. And it aligns DWARF with
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93763
--- Comment #1 from David Binderman ---
Reduced C code is:
typedef struct a a;
struct a {
a *b
} d;
e, k, ah, al;
f(aa) {
if (aa & 1)
goto g;
f(aa | 2);
g:
h();
}
l() {
{
f(072);
i(e, d, 92);
}
}
ag() {
{ i(e, d, 36);
77 matches
Mail list logo
