On Thu, May 14, 2020 at 11:53 PM Jason Merrill via Gcc-patches
wrote:
>
> There seemed to be general agreement last November that we would move to
> allowing C++11 features to be used in GCC 11; this patch implements that
> direction. Are changes needed anywhere else?
>
> ChangeLog
> 2020-05-14
On Fri, May 15, 2020 at 8:27 AM Uros Bizjak via Gcc-patches
wrote:
>
> On Fri, May 15, 2020 at 1:13 AM H.J. Lu wrote:
> >
> > The -mgeneral-regs-only option generates code that uses only the
> > general-purpose registers. It prevents the compiler from using vector
> > registers. But GCC may sti
PFACC/PFNACC 3dNow! instructions got their corresponding SSE alternative
in SSE3, so these can't be implemented with TARGET_MMX_WITH_SSE, which
implies SSE2. These instructions are only generated via builtins, and
since several 3dNow! insns have no corresponding SSE alternative,
we can't avoid MMX
When path splitting tries to detect a CFG diamond make sure it
is composed of normal (non-EH, not abnormal) edges. Otherwise
CFG manipulation later may fail.
Bootstrap / regtest running on x86_64-unknown-linux-gnu.
Richard.
2020-05-15 Richard Biener
PR tree-optimization/95133
On Thu, 14 May 2020, Jeff Law wrote:
> On Fri, 2020-05-08 at 06:44 -0700, H.J. Lu wrote:
> > CET has been added since GCC 8. This patch defaults CET run-time support
> > to auto. It enables CET run-time support if asssembler supports CET
> > instructions and multi-byte NOPs are enabled via SSE2.
Richard Biener via Gcc-patches writes:
> Note I think what's missing is some general blurb in our coding conventions
> as to how much of C++11 we are supposed to use in non-infrastructure parts
> of GCC (I expect things like hash-table.h to use more C++ features than,
> say, tree-ssa-alias.c).
I
Hi,
This patch adds support for demangling D functions annotated with the
new ownership/borrowing system attribute.
Following Jeff's advice from the last patch review, this has been
regression tested and committed to mainline. Firstly, as it is assumed
this falls under my D front-end maintainer
Hi.
Since we moved to git world and we're in the preparation for ChangeLog messages
being in git commit messages, I think it's the right time to also simplify mklog
script.
I'm sending a new version (which should eventually replace contrib/mklog and
contrib/mklog.pl).
Changes made in the versio
This improves the fix for PR92260 changing the number of vector
computation to the canonical one, not needing to look at the
using stmt.
Bootstrap / regtest running on x86_64-unknown-linux-gnu.
2020-05-15 Richard Biener
PR tree-optimization/92260
* tree-vect-slp.c (vect_get_co
On Wed, May 13, 2020 at 5:58 PM H.J. Lu wrote:
> > > > The question is, why STV pass creates its funny sequence? The original
> > > > sequence should be easily solved by storing DImode from XMM register
> > > > and (with patched gcc) pushing DImode value from the same XMM
> > > > register.
> > >
On Fri, May 15, 2020 at 10:30 AM Richard Sandiford
wrote:
>
> Richard Biener via Gcc-patches writes:
> > Note I think what's missing is some general blurb in our coding conventions
> > as to how much of C++11 we are supposed to use in non-infrastructure parts
> > of GCC (I expect things like hash
On 5/14/20 6:47 PM, Joseph Myers wrote:
On Thu, 14 May 2020, Martin Liška wrote:
On 5/13/20 7:53 PM, Joseph Myers wrote:
On Wed, 13 May 2020, Martin Liška wrote:
I'm sending the gcc-changelog relates scripts which should be added to
contrib
folder. The patch contains:
- git_check_commit.py -
On Fri, May 15, 2020 at 7:36 AM Christophe Lyon
wrote:
>
> On Thu, 14 May 2020 at 17:58, Ramana Radhakrishnan
> wrote:
> >
> > > static bool reg_needs_saving_p (unsigned reg)
> > > {
> > >unsigned long func_type = arm_current_func_type ();
> >
> > Ah ok , you needed it here.
>
> Yes sorry.
We're in stage1: PING^1
On 4/6/20 10:03 AM, Martin Liška wrote:
Hi.
We've started discussion the patch with Honza when we started working on
reproducibility of -fprofile-generate/use. The patch replaces pre-allocated
TOP N counters with a dynamical linked list allocation that happens during
pro
We're in stage1: PING^1
On 4/3/20 8:15 PM, Egeyar Bagcioglu wrote:
On 3/18/20 10:05 AM, Martin Liška wrote:
On 3/17/20 7:43 PM, Egeyar Bagcioglu wrote:
Hi Martin,
I like the patch. It definitely serves our purposes at Oracle and provides
another way to do what my previous patches did as we
Richard Biener writes:
> On Fri, May 15, 2020 at 10:30 AM Richard Sandiford
> wrote:
>>
>> Richard Biener via Gcc-patches writes:
>> > Note I think what's missing is some general blurb in our coding conventions
>> > as to how much of C++11 we are supposed to use in non-infrastructure parts
>> >
On Fri, May 15, 2020 at 11:58 AM Richard Sandiford
wrote:
>
> Richard Biener writes:
> > On Fri, May 15, 2020 at 10:30 AM Richard Sandiford
> > wrote:
> >>
> >> Richard Biener via Gcc-patches writes:
> >> > Note I think what's missing is some general blurb in our coding
> >> > conventions
> >>
Hi.
One fix of indentation that leads to -Wmisleading-indentation in Clang.
I'm going to install the patch.
Martin
gcc/ChangeLog:
2020-05-15 Martin Liska
* hsa-gen.c (get_symbol_for_decl): Fix misleading indentation
warning.
---
gcc/hsa-gen.c | 14 +++---
1 file ch
Hi,
The test commands for scanning optimization dump files
perform globbing on the argument that specifies the suffix
of the dump files to be scanned. This behavior is currently
undocumented. Furthermore, the current implementation of
"scan-dump" and related procedures yields an error whenever
the
Hello,
This patch fixes a bug in the arm backend where GCC generates invalid LDRD
instructions. The LDRD instruction requires the first transfer register to be
even, but GCC attempts to use odd registers here. For example, with the
following C code:
struct c {
double a;
} __attribut
This patch fixes a bug in which 8 and 16-bit vector shifts used the
wrong kind of extend, thus causing wrong results. It was simply a
thinko in the insn code, so easily fixed.
Andrew
P.S. Apologies for the "work-in-progress" tag on the commit subject.
Obviously that was meant to be removed,
M-profile related changes in GCC-10.
### Attachment also inlined for ease of reply###
diff --git a/htdocs/gcc-10/changes.html b/htdocs/gcc-10/changes.html
index
d1a7df0a9259292d097c1c3b9daeab56329ea435..57ca749da72ed64da37b3eb5404cf5cde8be44dd
100644
--- a/htdo
> -Original Message-
> From: Srinath Parvathaneni
> Sent: 15 May 2020 11:36
> To: gcc-patches@gcc.gnu.org
> Cc: Kyrylo Tkachov ; Richard Earnshaw
>
> Subject: [ARM][wwwdocs]: Document Armv8.1-M, Helium Intrinsics and
> Cortex-M55 changes.
>
> M-profile related changes in GCC-10.
Ok.
Another issue found when looking into PR94690 and its
regression/additional issues.
This patch lifts a restriction of 2.15.1.1. Data-sharing Attribute
Rules for Variables Referenced in a Construct.
OpenMP 4.5 had:
* The loop iteration variable(s) in the associated do-loop(s) of a
do, parallel
Hi Alex,
> -Original Message-
> From: Alex Coplan
> Sent: 15 May 2020 11:36
> To: gcc-patches@gcc.gnu.org
> Cc: nd ; ni...@redhat.com; Richard Earnshaw
> ; Ramana Radhakrishnan
> ; Kyrylo Tkachov
>
> Subject: [PATCH] [arm] Don't generate invalid LDRD insns
>
> Hello,
>
> This patch fix
On Fri, 2020-05-15 at 10:59 +0200, Martin Liška wrote:
> Hi.
>
> Since we moved to git world and we're in the preparation for
> ChangeLog messages
> being in git commit messages, I think it's the right time to also
> simplify mklog
> script.
>
> I'm sending a new version (which should eventually
> We're in stage1: PING^1
I wonder, did we somehow solved the issue with Firefox breaking due to
malloc instrumentation?
Honza
>
> On 4/6/20 10:03 AM, Martin Liška wrote:
> > Hi.
> >
> > We've started discussion the patch with Honza when we started working on
> > reproducibility of -fprofile-ge
On Fri, 15 May 2020 at 11:38, Ramana Radhakrishnan
wrote:
>
> On Fri, May 15, 2020 at 7:36 AM Christophe Lyon
> wrote:
> >
> > On Thu, 14 May 2020 at 17:58, Ramana Radhakrishnan
> > wrote:
> > >
> > > > static bool reg_needs_saving_p (unsigned reg)
> > > > {
> > > >unsigned long func_type
On 5/15/20 1:03 PM, Jan Hubicka wrote:
I wonder, did we somehow solved the issue with Firefox breaking due to
malloc instrumentation?
Yes, you proposed a patch:
https://hg.mozilla.org/try/rev/e1358ef2d82c035b12f8995712580c77bd9f8d43
Which I believe was sent to Firefox?
Martin
On 5/15/20 12:58 PM, David Malcolm wrote:
On Fri, 2020-05-15 at 10:59 +0200, Martin Liška wrote:
Hi.
Since we moved to git world and we're in the preparation for
ChangeLog messages
being in git commit messages, I think it's the right time to also
simplify mklog
script.
I'm sending a new versio
On Fri, May 15, 2020 at 12:53:41PM +0200, Tobias Burnus wrote:
> [Fortran] OpenMP 5 – permit more sharing clauses for SIMD (PR94690)
>
> gcc/fortran/
> PR fortran/94690
> * openmp.c (resolve_omp_do):
I'd hope Martin's script would reject such a commit. You didn't say what
you've chan
Armv8.1-M Mainline Security Extensions related changes in GCC-10.
### Attachment also inlined for ease of reply###
diff --git a/htdocs/gcc-10/changes.html b/htdocs/gcc-10/changes.html
index
57ca749da72ed64da37b3eb5404cf5cde8be44dd..10bf3b78c7769b73c808bd2c2fe60e
This adjusts the way we compute the stmt insert location for
invariants in BB vectorization context to deal with eventually
sharing invariant SLP nodes for multiple uses. We can no longer
use a single use stmt location then but there's a simple way out.
Bootstrap and regtest running on x86_64-unk
On Fri, May 15, 2020 at 10:59:56AM +0200, Martin Liška wrote:
> Hi.
>
> Since we moved to git world and we're in the preparation for ChangeLog
> messages
> being in git commit messages, I think it's the right time to also simplify
> mklog
> script.
>
> I'm sending a new version (which should ev
On Fri, 2020-05-15 at 13:20 +0200, Martin Liška wrote:
> On 5/15/20 12:58 PM, David Malcolm wrote:
> > On Fri, 2020-05-15 at 10:59 +0200, Martin Liška wrote:
> > > Hi.
> > >
> > > Since we moved to git world and we're in the preparation for
> > > ChangeLog messages
> > > being in git commit messag
On 5/15/20 2:42 PM, Marek Polacek wrote:
I actually use mklog -i all the time. But I can work around it if it
disappears.
Ah, I can see a consumer.
There's an updated version that supports that.
For the future, will you still use the option? Wouldn't be better
to put the ChangeLog content dir
When defaulting CET run-time support to auto, check if -fcf-protection
works. Even if the stage1 GCC doesn't support -fcf-protection, since
the final GCC does, CET run-time support will be enabled by default if
binutils support CET.
config/
PR bootstrap/95147
* cet.m4 (GCC_CET_FL
On Fri, May 15, 2020 at 03:12:27PM +0200, Martin Liška wrote:
> On 5/15/20 2:42 PM, Marek Polacek wrote:
> > I actually use mklog -i all the time. But I can work around it if it
> > disappears.
>
> Ah, I can see a consumer.
> There's an updated version that supports that.
>
> For the future, wil
Hi Frederik!
(We had internally discussed this.)
I can't formally approve testsuite patches, but did a review anyway:
On 2020-05-15T12:31:54+0200, Frederik Harwath wrote:
> The test commands for scanning optimization dump files
> perform globbing on the argument that specifies the suffix
> of t
On 5/14/20 3:17 PM, Arseny Solokha wrote:
Hi,
- if (TREE_CODE (nt) == TREE_VEC)
+ if (TREE_CODE (nt) == TREE_VEC || TREE_CODE (nt) == TREE_VEC)
Shouldn't there be
if (TREE_CODE (ot) == TREE_VEC || TREE_CODE (nt) == TREE_VEC)
+ else if (TYPE_P (nt) || TYPE_P (nt))
And here:
el
Hi Ian,
> On Thu, May 14, 2020 at 12:43 PM Rainer Orth
> wrote:
>>
>> > This libgo patch builds the syscall test with -static. This avoids
>> > problems finding libgo.so when running the test as root, which invokes
>> > the test as a child process in various limited environments. This
>> > fixe
Hello, gentle maintainer.
This is a message from the Translation Project robot.
A revised PO file for textual domain 'cpplib' has been submitted
by the Swedish team of translators. The file is available at:
https://translationproject.org/latest/cpplib/sv.po
(This file, 'cpplib-10.1-b202002
cpplib-10.1-b20200209.sv.po.gz
Description: Binary data
The Translation Project robot, in the
name of your translation coordinator.
>> > We've moved more and more to stronly-typed data structures
>> > so I'd not like to see 'auto' everywhere - it should be still
>> > obvious what kind of objects we're working with where they
>> > matter. IMHO they do not matter for example for iterators.
>> > I don't care about the iterator ty
Also change XMM register constraint from "x" to "v" in FP push insns.
gcc/ChangeLog:
2020-05-15 Uroš Bizjak
* config/i386/i386.md (SWI48DWI): New mode iterator.
(*push2): Allow XMM registers.
(*pushdi2_rex64): Ditto.
(*pushsi2_rex64): Ditto.
(*pushsi2): Ditto.
(push XM
On 5/15/20 2:59 AM, Martin Liška wrote:
Hi.
Since we moved to git world and we're in the preparation for ChangeLog
messages
being in git commit messages, I think it's the right time to also
simplify mklog
script.
I'm sending a new version (which should eventually replace contrib/mklog
and c
On May 15, 2020 3:16:38 PM GMT+02:00, "H.J. Lu" wrote:
>When defaulting CET run-time support to auto, check if -fcf-protection
>works. Even if the stage1 GCC doesn't support -fcf-protection, since
>the final GCC does, CET run-time support will be enabled by default if
>binutils support CET.
OK.
On 5/15/20 3:22 PM, Marek Polacek wrote:
On Fri, May 15, 2020 at 03:12:27PM +0200, Martin Liška wrote:
On 5/15/20 2:42 PM, Marek Polacek wrote:
I actually use mklog -i all the time. But I can work around it if it
disappears.
Ah, I can see a consumer.
There's an updated version that supports
On Thu, 2020-05-14 at 18:51 +0200, Jakub Jelinek wrote:
> On Thu, May 14, 2020 at 10:10:55AM -0600, Jeff Law wrote:
> > On Tue, 2020-05-12 at 10:12 +0200, Jakub Jelinek wrote:
> > > Hi!
> > >
> > > In the following testcase, store_expr of e.g. 97 bytes long string literal
> > > into 1MB long array
On Tue, 2020-05-05 at 20:16 +0200, Stefan Schulze Frielinghaus via Gcc-patches
wrote:
> While bootstrapping GCC on S/390 with --enable-checking=release several
> warnings about use of uninitialized variables bitpos, bitregion_start, and
> bitregion_end of function pass_store_merging::process_store
The attached patch fixes many GCC and G++ tests for 16-bit targets. These
targets can have the following properties:
- "int", "size_t", "ptrdiff_t", "void *" are 16-bit types
- sizeof(int) == sizeof(short)
These properties cause problems for a number of tests in the testsuite,
where int is often a
On Fri, May 15, 2020 at 3:15 AM Richard Biener
wrote:
> > +# When bootstrapping with GCC, build stage 1 in C++11 mode to ensure
> that a
> > +# C++11 compiler can still start the bootstrap.
> > if test "$enable_bootstrap:$GXX" = "yes:yes"; then
> > + CXX="$CXX -std=gnu++11"
>
> So I just spotte
On Fri, May 15, 2020 at 5:58 AM Richard Sandiford
wrote:
> Richard Biener writes:
> > On Fri, May 15, 2020 at 10:30 AM Richard Sandiford
> > wrote:
> >>
> >> Richard Biener via Gcc-patches writes:
> >> > Note I think what's missing is some general blurb in our coding
> conventions
> >> > as to
My GCC 10 patch for 93286 fixed the missing piece in tsubst's handling of
lists vs. that in tsubst_copy_and_build, but it would be better to share the
code between them.
Tested x86_64-pc-linux-gnu, applying to trunk.
gcc/cp/ChangeLog
2020-05-15 Jason Merrill
PR c++/93286 - ICE with __
On May 15, 2020 7:30:38 PM GMT+02:00, Jason Merrill wrote:
>On Fri, May 15, 2020 at 3:15 AM Richard Biener
>
>wrote:
>
>> > +# When bootstrapping with GCC, build stage 1 in C++11 mode to
>ensure
>> that a
>> > +# C++11 compiler can still start the bootstrap.
>> > if test "$enable_bootstrap:$GXX"
On Wed, 15 Apr 2020, Patrick Palka wrote:
> On Wed, 15 Apr 2020, Martin Sebor via Gcc-patches wrote:
> > On 4/13/20 8:43 PM, Jason Merrill wrote:
> > > On 4/12/20 5:49 PM, Martin Sebor wrote:
> > > > On 4/10/20 8:52 AM, Jason Merrill wrote:
> > > > > On 4/9/20 4:23 PM, Martin Sebor wrote:
> > > > >
On Fri, 2020-05-15 at 18:26 +0100, Jozef Lawrynowicz wrote:
> The attached patch fixes many GCC and G++ tests for 16-bit targets. These
> targets can have the following properties:
> - "int", "size_t", "ptrdiff_t", "void *" are 16-bit types
> - sizeof(int) == sizeof(short)
>
> These properties cau
Tests that use the __int128 type need to use the int128 selector.
2020-05-15 Segher Boessenkool
gcc/testsuite/
* gcc.target/powerpc/vec-gnb-0.c: Use int128 effective target.
* gcc.target/powerpc/vec-gnb-1.c: Ditto.
* gcc.target/powerpc/vec-gnb-2.c: Ditto.
* gcc.
2020-05-15 Segher Boessenkool
gcc/testsuite/
* gcc.target/powerpc/cnttzdm-0.c: Use lp64.
---
gcc/testsuite/gcc.target/powerpc/cnttzdm-0.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/gcc/testsuite/gcc.target/powerpc/cnttzdm-0.c
b/gcc/testsuite/gcc.target/powerpc/cnttzdm-0.c
ind
Some fixes for -mcpu=future, mostly testsuite. This also cleans up
some other testsuite problems.
Tested on powerpc64-linux {-m32,-m64}; committing to trunk. This
hopefully cleans up some of the AIX problems here as well.
Segher
Segher Boessenkool (5):
rs6000/testsuite: Use -mdejagnu-cpu=
The powerpc64 effective target unfortunately does not mean the target
has 64-bit instructions enabled (i.e., -mpowerpc64): instead, it means
that the assembler supports it.
Let's use the lp64 effective target instead for these tests.
2020-05-15 Segher Boessenkool
gcc/testsuite/
* gcc.
A bunch of new cases snuck in.
2020-05-15 Segher Boessenkool
gcc/testsuite/
* gcc.target/powerpc/pdep-0.c: Change -mcpu= to -mdejagnu-cpu=.
* gcc.target/powerpc/pdep-1.c: Ditto.
* gcc.target/powerpc/pextd-0.c: Ditto.
* gcc.target/powerpc/pextd-1.c: Ditto.
BU_FUTURE_MISC_2 is (currently) only used for instructions that require
64-bit registers.
2020-05-15 Segher Boessenkool
* config/rs6000/rs6000-builtin.def (BU_FUTURE_MISC_2): Also require
RS6000_BTM_POWERPC64.
---
gcc/config/rs6000/rs6000-builtin.def | 3 ++-
1 file changed, 2
Here's a new attempt to finally fix this PR and any known fallout.
In order to handle division by zero in declarations, but still accept the
code snippet adapted from 521.wrf_r (from spec2017), I removed the hunk
that was added to fix PR94399, and deferred the handling to a later stage.
One case
I think I completed this evolution.
I eventually used ref to node pointer as much as possible and even use
move semantic on it.
My prerequisite for this to work is that nullptr can be assign on the
fancy pointer and that a fancy pointer to __node_type is assignable
implicitely to a fancy poi
On 5/15/20 2:21 PM, Richard Biener wrote:
On May 15, 2020 7:30:38 PM GMT+02:00, Jason Merrill wrote:
On Fri, May 15, 2020 at 3:15 AM Richard Biener
wrote:
+# When bootstrapping with GCC, build stage 1 in C++11 mode to
ensure
that a
+# C++11 compiler can still start the bootstrap.
if tes
On 5/14/20 4:19 PM, Patrick Palka wrote:
We sometimes fail to reject a invalid non-dependent operand to decltype
when inside a template, because finish_decltype_type resolves the
decltype to the TREE_TYPE of the operand before we ever instantiate and
fully process the operand. Fix this by adding
On Fri, May 15, 2020 at 12:31 PM Srinath Parvathaneni
wrote:
>
> Armv8.1-M Mainline Security Extensions related changes in GCC-10.
>
>
> ### Attachment also inlined for ease of reply
> ###
>
>
> diff --git a/htdocs/gcc-10/changes.html b/htdocs/gcc-10/changes.html
>
On Fri, May 15, 2020 at 6:42 AM Rainer Orth
wrote:
>
> > On Thu, May 14, 2020 at 12:43 PM Rainer Orth
> > wrote:
> >>
> >> > This libgo patch builds the syscall test with -static. This avoids
> >> > problems finding libgo.so when running the test as root, which invokes
> >> > the test as a chil
On Fri, 15 May 2020, Jozef Lawrynowicz wrote:
> The attached patch fixes many GCC and G++ tests for 16-bit targets. These
> targets can have the following properties:
> - "int", "size_t", "ptrdiff_t", "void *" are 16-bit types
> - sizeof(int) == sizeof(short)
Some of the tests are disabled by the
Besides better buffer overflow checking, the new GCC 10 attribute
access also provides an opportunity to detect other kinds of bugs,
including uninitialized accesses by user-defined functions.
The attached patch implements this enhancement.
In addition, the closely related PR 10138 requests that
Adds support for DMGL_RET_POSTFIX in D demangler, so it shows the type
of the declared variable, or function return type. Postfix notation is
used with space.
libiberty/ChangeLog:
* d-demangle.c: Add DMGL_RET_POSTFIX support.
* testsuite/d-demangle-expected: Add new tests.
Signed-off-by: Witold
On 5/15/20 8:08 AM, Richard Sandiford wrote:
We've moved more and more to stronly-typed data structures
so I'd not like to see 'auto' everywhere - it should be still
obvious what kind of objects we're working with where they
matter. IMHO they do not matter for example for iterators.
I don't care
On Fri, May 15, 2020 at 9:47 PM Martin Sebor wrote:
> On 5/15/20 8:08 AM, Richard Sandiford wrote:
> We've moved more and more to stronly-typed data structures
> so I'd not like to see 'auto' everywhere - it should be still
> obvious what kind of objects we're working with where th
A couple minor improvements to the H8 port I spotted while doing the cc0->CC_REG
transition.
First is consolidation of 3 peepholes into a single peephole using a mode
iterator. This has zero impact on the code we generate, but means fewer
patterns
that I ultimately have to convert.
Second is t
On May 15, 2020 11:53:42 PM GMT+02:00, Jason Merrill wrote:
>On 5/15/20 2:21 PM, Richard Biener wrote:
>> On May 15, 2020 7:30:38 PM GMT+02:00, Jason Merrill
> wrote:
>>> On Fri, May 15, 2020 at 3:15 AM Richard Biener
>>>
>>> wrote:
>>>
> +# When bootstrapping with GCC, build stage 1 in C++11
76 matches
Mail list logo
