On 5/11/20 2:44 PM, Richard Biener wrote:
Hmm, I think the fix is to clear DECL_NOT_GIMPLE_REG_P instead
where the code clears TREE_ADDRESSABLE of 'arg'
Ah, you are right. There's a patch that I've just tested.
Patch can bootstrap on x86_64-linux-gnu and survives regression tests.
Ready to be
On Fri, May 08, 2020 at 11:48:34AM -0400, Nathan Sidwell wrote:
> 2020-05-08 Nathan Sidwell
>
> gcc/cp/
> * parser.c (cp_lexer_set_source_position_from_token): EOF has a
> location too.
This change:
> --- c/gcc/cp/parser.c
> +++ w/gcc/cp/parser.c
> @@ -895,10 +895,7 @@ cp_le
On Tue, May 12, 2020 at 9:04 AM Martin Liška wrote:
>
> On 5/11/20 2:44 PM, Richard Biener wrote:
> > Hmm, I think the fix is to clear DECL_NOT_GIMPLE_REG_P instead
> > where the code clears TREE_ADDRESSABLE of 'arg'
>
> Ah, you are right. There's a patch that I've just tested.
>
> Patch can boots
Hi!
This attempts to implement what the OpenMP 5.0 spec in declare target section
says as ammended by the 5.1 changes so far (related to device_type(host)),
except
that it doesn't have the device(ancestor: ...) handling yet because we do not
support it yet, and I've left so far out the except lam
Hi!
The r11-15 change broke this testcase, as it now asserts type is equal to
the type of the DECL_VALUE_EXPR, but for DECL_OMP_PRIVATIZED_MEMBER artificial
vars mapping to bitfields it wasn't. Fixed by changing the
DECL_OMP_PRIVATIZED_MEMBER var type in that case.
Bootstrapped/regtested on x86_
Hi!
In the following testcase, store_expr of e.g. 97 bytes long string literal
into 1MB long array is implemented by copying the 97 bytes from .rodata
section, followed by clearing the remaining bytes. But, as the STRING_CST
has type char[1024*1024], we actually allocate whole 1MB in .rodata sect
Hi Jakub,
> On Fri, May 08, 2020 at 11:48:34AM -0400, Nathan Sidwell wrote:
>> 2020-05-08 Nathan Sidwell
>>
>> gcc/cp/
>> * parser.c (cp_lexer_set_source_position_from_token): EOF has a
>> location too.
>
> This change:
>
>> --- c/gcc/cp/parser.c
>> +++ w/gcc/cp/parser.c
>> @@ -
On Mon, 11 May 2020, Joseph Myers wrote:
> On Fri, 8 May 2020, Richard Biener wrote:
>
> > The IFNs are supposed to match fmin and fmax from the C standard which
> > IIRC have IEEE semantics.
>
> fmin and fmax have IEEE (2008) semantics (where an sNaN operand results in
> a qNaN result with "i
On Mai 11 2020, Jason Merrill via Gcc-patches wrote:
> If a program has no other dependencies on libstdc++, we shouldn't require it
> just for __cxa_pure_virtual, which is only there to give a prettier
> diagnostic before crashing the program; resolving the reference to NULL will
> also crash, jus
I'm also CCing gcc-patches and fortran ML.
Martin
On 5/12/20 11:05 AM, Martin Liška wrote:
Hi.
Thanks to Jakub, we finally set up an experimental environment:
gcc.gnu.org/home/gccadmin/gcc-reposurgeon-8.git
The repository now contains a new pre-commit hook that validates
the git commit format
Hi!
Looks fine to me... Just the same generic things as before, things we
can improve later, not even limited to this series:
On Sat, May 09, 2020 at 08:16:26AM -0500, Bill Schmidt wrote:
> * config/rs6000/altivec.md (UNSPEC_VSTRIR): New constant.
> (UNSPEC_VSTRIL): Likewise.
Names
On Tue, May 12, 2020 at 7:27 AM Hongtao Liu wrote:
>
> Documents operand modifiers which are available in asm stmt but
> missing in document.
>
> | Modifier | Description | Available in asm stmt | Existed in documentation |
> | --- | --- | --- | - |
> | L,W,B,Q,S,T | print the opcode su
On Thu, Apr 23, 2020 at 03:43:47PM +0200, Tobias Burnus wrote:
> On 4/20/20 11:33 PM, Thomas Schwinge wrote:
> > Really 'GOMP_MAP_DELETE', or should that rather be 'GOMP_MAP_RELEASE'?
>
> Depends on the previous item, i.e. 'delete:' vs. 'release:/from:/…'
>
> Rather obvious – OK?
>
> Tobias
>
>
On Fri, May 08, 2020 at 05:09:07PM +0200, Tobias Burnus wrote:
> I was thinking of simply marking them as
> "nflags |= GOVD_FIRSTPRIVATE" but I am not sure whether
> that would always make sense, either. In any case, a
> simple usage would bypass the
> "implicit mapping of assumed size array"
> dia
This removes debug-bind resets aka
# DEBUG b = NULL
when the reset variable is otherwise unused. I've gathered statistics
for a single TU, fold-const.ii which at -O2 -g shows
28 ssa "dead debug bind reset" 1
34 einline "dead debug bind reset" 340
54 release_ssa "dead debug bind reset" 176
54
On Thu, Apr 23, 2020 at 08:52:39AM +0200, Tobias Burnus wrote:
> [Fortran] OpenMP - permit lastprivate in distribute + SIMD fixes (PR94690)
>
> PR fortran/94690
> * openmp.c (OMP_DISTRIBUTE_CLAUSES): Add OMP_CLAUSE_LASTPRIVATE.
> * trans-openmp.c (gfc_trans_omp_do): Don't add pri
This fixes an oversight in the new canonicalization code for packable types:
it does not take into account the scalar storage order.
Tested on x86-64/Linux and SPARC/Solaris, applied on the mainline.
2020-05-12 Eric Botcazou
PR ada/95035
* gcc-interface/utils.c (packable_typ
Uninitialized global variables are put in the .bss section since the -fno-common
change, the attached patch prevents region-attribute-misuse.c failing if a .bss
section is in the assembler output.
Committed as obvious.
>From 89aa37dc3c71666d0ff05e96ea84e195d049a226 Mon Sep 17 00:00:00 2001
From: J
The attached patch implements ASM_OUTPUT_ALIGNED_DECL_LOCAL for msp430. The
default handler needs to be overridden so local common symbols which need
their own section (e.g. variables with the "noinit" attribute) will be placed
in that section rather than the common block.
This fixes "gcc.c-tortur
The testcase only works for little-endian, mark it so.
2020-05-12 Richard Biener
* gcc.dg/torture/pr94988.c: Disable runtime test for
* non-little-endian.
---
gcc/testsuite/gcc.dg/torture/pr94988.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/gcc/testsuite/gcc.dg/tort
On Mon, May 11, 2020 at 10:56 PM Bill Schmidt wrote:
>
> On 5/11/20 9:48 AM, David Edelsohn wrote:
> > On Sun, May 10, 2020 at 9:14 AM Bill Schmidt wrote:
> >> From: Kelvin Nilsen
> >>
> >> Add new insns vextdu[bhw]vlx, vextddvlx, vextdu[bhw]vhx, and
> >> vextddvhx, along with built-in access an
On Mon, May 11, 2020 at 11:45:09AM -0500, Bill Schmidt wrote:
> On 5/8/20 6:51 PM, Segher Boessenkool wrote:
> >On Fri, May 08, 2020 at 08:17:18AM -0500, Bill Schmidt wrote:
> >>From: Kelvin Nilsen
> >>
> >>Add support for new scalar instructions for counting leading or
> >>trailing zeros under co
On Fri, May 8, 2020 at 6:11 AM H.J. Lu wrote:
>
> Don't perform CET run-time check for host when cross compiling. Instead,
> enable CET in cross compiler if possible so that it will run on both CET
> and non-CET hosts.
>
> config/
>
> PR bootstrap/94998
> * cet.m4 (GCC_CET_HOST_FL
On Tue, 12 May 2020, Richard Biener wrote:
>
> This removes debug-bind resets aka
>
> # DEBUG b = NULL
>
> when the reset variable is otherwise unused. I've gathered statistics
> for a single TU, fold-const.ii which at -O2 -g shows
>
> 28 ssa "dead debug bind reset" 1
> 34 einline "dead debu
On 5/12/20 4:54 AM, Segher Boessenkool wrote:
Hi!
Looks fine to me... Just the same generic things as before, things we
can improve later, not even limited to this series:
On Sat, May 09, 2020 at 08:16:26AM -0500, Bill Schmidt wrote:
* config/rs6000/altivec.md (UNSPEC_VSTRIR): New con
On Tue, 12 May 2020 at 10:28, Andreas Schwab wrote:
>
> On Mai 11 2020, Jason Merrill via Gcc-patches wrote:
>
> > If a program has no other dependencies on libstdc++, we shouldn't require it
> > just for __cxa_pure_virtual, which is only there to give a prettier
> > diagnostic before crashing the
Hi!
On Tue, May 12, 2020 at 02:48:40PM +0800, luoxhu wrote:
> diff --git a/gcc/testsuite/gcc.target/powerpc/doloop-2.c
> b/gcc/testsuite/gcc.target/powerpc/doloop-2.c
> new file mode 100644
> index 000..dc8516bb0ab
> --- /dev/null
> +++ b/gcc/testsuite/gcc.target/powerpc/doloop-2.c
> @@ -
Please find attached for PR93497. This patch was posted as a comment to
the PR, I've checked it added a test case. It has the side affect of
changing the errors for three other test cases which have modified
accordingly.
The commit message is as follows:
fortran : ICE in gfc_conv_array_constr
gcc/ChangeLog:
2020-05-12 Uroš Bizjak
PR target/95046
* config/i386/mmx.md (v2sf2): New insn pattern.
(*mmx_v2sf2): New insn_and_split pattern.
(*mmx_nabsv2sf2): Ditto.
(*mmx_andnotv2sf3): New insn pattern.
(*mmx_v2sf3): Ditto.
* config/i386/i386.md (absneg_op): New
On Sat, 2020-05-09 at 08:43 -0700, H.J. Lu wrote:
> Since on Intel CET enabled host, dlopen in Intel CET enabled applications
> fails on shared libraries which aren't Intel CET enabled, enable Intel
> CET in libcc1 on Intel CET enabled host.
>
> * Makefile.am (AM_CXXFLAGS): Add $(CET_HOST_FL
On Sat, 2020-05-09 at 08:43 -0700, H.J. Lu wrote:
> Since on Intel CET enabled host, dlopen in Intel CET enabled applications
> fails on shared libraries which aren't Intel CET enabled, compile with
> -fcf-protection on Intel CET enabled host when jit is enabled to enable
> Intel CET on libgccjit.
On Sat, 2020-05-09 at 08:43 -0700, H.J. Lu wrote:
> Since on Intel CET enabled host, dlopen in Intel CET enabled applications
> fails on shared libraries which aren't Intel CET enabled, compile with
> -fcf-protection on Intel CET enabled host when jit is enabled to enable
> Intel CET on libgccjit.
On Sat, 2020-05-09 at 08:43 -0700, H.J. Lu wrote:
> Since on Intel CET enabled host, dlopen in Intel CET enabled applications
> fails on shared libraries which aren't Intel CET enabled, compile with
> -fcf-protection on Intel CET enabled host when jit is enabled to enable
> Intel CET on libgccjit.
On Sat, 2020-05-09 at 08:43 -0700, H.J. Lu wrote:
> Since on Intel CET enabled host, dlopen in Intel CET enabled applications
> fails on shared libraries which aren't Intel CET enabled, compile with
> -fcf-protection on Intel CET enabled host when jit is enabled to enable
> Intel CET on libgccjit.
On Tue, 2020-05-05 at 16:08 -0400, Nathan Sidwell wrote:
> I discovered that libitm:
> (a) declares __cxa_allocate_exception and friends directly,
> (b) doesn't mark them as 'throw()'
> (c) doesn't mark the replacment fns _ITM_$foo as nothrow either
>
> We happen to get away with it because of cod
On Fri, 2020-05-08 at 13:10 -0700, H.J. Lu wrote:
> When --enable-cet is used to configure GCC, enable Intel CET in target
> zlib.
>
> * Makefile.am (AM_CFLAGS): New.
> * configure.ac (CET_FLAGS): Add GCC_CET_FLAGS and AC_SUBST.
> * Makefile.in: Regenerated.
> * aclocal.m4:
On Thu, 2020-04-23 at 16:05 -0600, Martin Sebor wrote:
> On 4/23/20 9:42 AM, Jeff Law wrote:
> > On Wed, 2020-04-22 at 15:36 -0600, Martin Sebor via Gcc-patches wrote:
> > > When computing the size of an object with a flexible array member
> > > the object size pass doesn't consider that the initia
This adds an abbreviated function template version of the testcase in
PR78752, which seems to already be fixed.
gcc/testsuite/ChangeLog:
PR c++/78752
* g++.dg/cpp2a/concepts-pr78752-2.C: New test.
---
.../g++.dg/cpp2a/concepts-pr78752-2.C | 21 +++
2 files
gcc/ChangeLog:
2020-05-12 Uroš Bizjak
PR target/95046
* config/i386/mmx.md (fmav2sf4): New insn pattern.
(fmsv2sf4): Ditto.
(fnmav2sf4): Ditto.
(fnmsv2sf4): Ditto.
testsuite/ChangeLog:
2020-05-12 Uroš Bizjak
PR target/95046
* gcc.target/i386/pr95046-3.c: New t
On Fri, 2020-05-08 at 06:11 -0700, H.J. Lu via Gcc-patches wrote:
> Don't perform CET run-time check for host when cross compiling. Instead,
> enable CET in cross compiler if possible so that it will run on both CET
> and non-CET hosts.
>
> config/
>
> PR bootstrap/94998
> * cet.m4 (
gcc/ChangeLog:
2020-05-12 Uroš Bizjak
PR target/95046
* config/i386/mmx.md (copysignv2sf3): New expander.
(xorsignv2sf3): Ditto.
(signbitv2sf3): Ditto.
testsuite/ChangeLog:
2020-05-12 Uroš Bizjak
PR target/95046
* gcc.target/i386/pr95046-4.c: New test.
Bootstrapp
On Fri, 2020-05-08 at 19:51 +0200, Andreas Krebbel via Gcc-patches wrote:
> When compiling with -mbackchain -fstack-clash-protection currently no
> probes are emitted. This patch adjusts the "allocate_stack" expander
> to call anti_adjust_stack_and_probe_stack_clash when needed. In order
> to do t
Hi!
On Mon, May 11, 2020 at 09:56:14PM -0500, Bill Schmidt wrote:
> On 5/11/20 9:48 AM, David Edelsohn wrote:
> >On Sun, May 10, 2020 at 9:14 AM Bill Schmidt
> >wrote:
> >> * config/rs6000/altivec.md (UNSPEC_EXTRACTL): New constant.
> >> (UNSPEC_EXTRACTR): Likewise.
> >>
luoxhu writes:
> + /* Fold (add -1; zero_ext; add +1) operations to zero_ext. i.e:
> +
> + 73: r145:SI=r123:DI#0-0x1
> + 74: r144:DI=zero_extend (r145:SI)
> + 75: r143:DI=r144:DI+0x1
> + ...
> + 31: r135:CC=cmp (r123:DI,0)
> + 72: {pc={(r143:DI!=0x1)?L70:pc};r143
On 5/12/20 1:21 PM, Segher Boessenkool wrote:
Hi!
On Mon, May 11, 2020 at 09:56:14PM -0500, Bill Schmidt wrote:
On 5/11/20 9:48 AM, David Edelsohn wrote:
On Sun, May 10, 2020 at 9:14 AM Bill Schmidt
wrote:
* config/rs6000/altivec.md (UNSPEC_EXTRACTL): New constant.
(UNSPEC_
On Tue, May 12, 2020 at 1:12 AM Richard Biener via Gcc-patches
wrote:
>
> On Tue, May 12, 2020 at 9:04 AM Martin Liška wrote:
> >
> > On 5/11/20 2:44 PM, Richard Biener wrote:
> > > Hmm, I think the fix is to clear DECL_NOT_GIMPLE_REG_P instead
> > > where the code clears TREE_ADDRESSABLE of 'arg
On Tue, May 12, 2020 at 11:57 AM H.J. Lu wrote:
>
> On Tue, May 12, 2020 at 1:12 AM Richard Biener via Gcc-patches
> wrote:
> >
> > On Tue, May 12, 2020 at 9:04 AM Martin Liška wrote:
> > >
> > > On 5/11/20 2:44 PM, Richard Biener wrote:
> > > > Hmm, I think the fix is to clear DECL_NOT_GIMPLE_R
I really don't get it why so many corporate webmasters do not put
redirects in place at least for a while. Luckily we've got Google.
Pushed.
Gerald
---
htdocs/readings.html | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/htdocs/readings.html b/htdocs/readings.html
index 086b
Hi!
On Tue, May 12, 2020 at 12:06:25PM -0700, H.J. Lu wrote:
> Excess errors:
> cc1: error: '-fsanitize=address' is incompatible with
> '-fsanitize=kernel-address'
asan.exp adds -fsanitize=address which is incompatible with
-fsanitize=kernel-address,
so we need to disable it first.
Tested on x8
Update STV pass to properly count cost of XMM register push. In 32-bit
mode, to convert XMM register push in DImode, we do an XMM store in
DImode, followed by 2 memory pushes in SImode, instead of 2 integer
register pushes in SImode. To convert XM register push in SImode, we
do an XMM register to
I noticed that we don't implement [basic.lookup.argdep]/3: quite correctly;
it says "If X (the lookup set produced by unqualified lookup) contains
-- a block-scope function declaration that is not a using-declaration
[...]
then Y (the lookup set produced by ADL) is empty."
but we were still perform
On 5/12/20 4:18 PM, Marek Polacek wrote:
I noticed that we don't implement [basic.lookup.argdep]/3: quite correctly;
it says "If X (the lookup set produced by unqualified lookup) contains
-- a block-scope function declaration that is not a using-declaration
[...]
then Y (the lookup set produced b
This makes sure that gigi is prepared to handle more aggregates in the special
memset code path.
Tested on x86-64/Linux, applied on the mainline.
2020-05-12 Eric Botcazou
* sem_aggr.ads (Is_Single_Aggregate): New function.
* sem_aggr.adb (Is_Others_Aggregate): Use local vari
My recent C++ parser change to pay attention to EOF location uncovered a
separate bug. The preprocesor's EOF logic would set the EOF location to
be the beginning of the last line of text in the file -- not the 'line'
after that, which contains no characters. Mostly. This fixes things so
that
The C/C++ bindings generated by means of -fdump-ada-spec always contain with
and use clauses for Interfaces.C, but they can be unused in some cases so make
sure to avoid warning about that.
Tested on x86-64/Linux, applied on the mainline.
2020-05-12 Eric Botcazou
c-family/
* c-ada-
On Mon, Apr 27, 2020 at 10:08 AM Craig Blackmore
wrote:
> Thanks for the review. I have updated the following patch with those changes.
This looks good, and the tree is open for development work again, so I
committed both parts 1 and 2 and pushed it.
One weird thing is that while the patch progr
On Sun, Apr 12, 2020 at 7:54 PM Kito Cheng wrote:
> On Sat, Apr 11, 2020 at 1:48 AM Jim Wilson wrote:
> > Do we really need this now? It is a new feature not a bug fix, so it
> > might be better to wait until we reach stage1. We have limited time
> > to test this before the gcc-10 release.
>
>
-fsplit-dwarf is similar to -gsplit-dwarf, but does not enable debugging
information by itself. This makes it easier to be plugged into a build
system without worrying that unnecessary debugging information may be
generated.
2020-05-12 Fangrui Song
PR debug/95096
* common.opt:
This fixes a bug reported to the RISC-V sw-dev mailing list late last year.
https://groups.google.com/a/groups.riscv.org/forum/#!topic/sw-dev/JV5Jdh4UjVw
Keith Packard wote the obvious patch to fix it. I tested it with cross builds
for riscv32-newlib and riscv64-linux. There were no regressions.
On Tue, May 12, 2020 at 2:24 PM Nathan Sidwell wrote:
>
> My recent C++ parser change to pay attention to EOF location uncovered a
> separate bug. The preprocesor's EOF logic would set the EOF location to
> be the beginning of the last line of text in the file -- not the 'line'
> after that, whic
Hi.
On 05/11, Richard Biener wrote:
> On Fri, May 8, 2020 at 7:11 PM Jeff Law via Gcc-patches
> wrote:
> >
> > On Fri, 2020-05-08 at 13:06 -0300, Giuliano Belinassi via Gcc-patches wrote:
> > > Hi,
> > >
> > > This patch Refactors tree-vrp.c to eliminate all global variables except
> > > 'x_vrp_v
This fixes SFINAE when substitution yields an invalid delete-expression
due to the pertinent deallocation function being marked deleted or
otherwise inaccessible.
We need to check for an erroneous result from build_op_delete_call and
exit early in that case, so that we don't build a COND_EXPR arou
Hi,
Updated to v3 according to 2/4's param change.
BR,
Kewen
---
gcc/ChangeLog
2020-MM-DD Kewen Lin
* tree-ssa-loop-ivopts.c (struct iv_group): New field reg_offset_p.
(struct iv_cand): New field reg_offset_p.
(struct ivopts_data): New field consider_reg_offs
Hi,
I'd like to ping this patch as well as its sblings. Thanks in advance.
1/4 v3 https://gcc.gnu.org/pipermail/gcc-patches/2020-February/540171.html
2/4 v3 https://gcc.gnu.org/pipermail/gcc-patches/2020-March/541387.html
3/4 v3 https://gcc.gnu.org/pipermail/gcc-patches/2020-May/545643.html
BR,
On Wed, 13 May 2020 at 02:24, H.J. Lu via Gcc-patches
wrote:
>
> On Tue, May 12, 2020 at 2:24 PM Nathan Sidwell wrote:
> >
> > My recent C++ parser change to pay attention to EOF location uncovered a
> > separate bug. The preprocesor's EOF logic would set the EOF location to
> > be the beginning
On Wed, May 13, 2020 at 1:40 AM Fangrui Song via Gcc-patches
wrote:
>
> -fsplit-dwarf is similar to -gsplit-dwarf, but does not enable debugging
> information by itself. This makes it easier to be plugged into a build
> system without worrying that unnecessary debugging information may be
> genera
66 matches
Mail list logo
