On Tue, 14 Apr 2020, Jan Hubicka wrote:
> >
> > But we're using it in indirect_ref_may_alias_decl_p as
> >
> > /* If second reference is view-converted, give up now. */
> > if (same_type_for_tbaa (TREE_TYPE (dbase2), TREE_TYPE (ptrtype2)) !=
> > 1)
> > return true;
> >
> >
Hi!
As reported in the PR, GCC 10 (and also 9.3.1 but not 9.3.0) fails to build
when using older binutils which lack LSE support, because those instructions
are used in libgcc.
Thanks to Kyrylo's hint, the following patches (hopefully) allow it to build
even with older binutils by using .inst dire
On 4/9/20 2:44 PM, Jan Hubicka wrote:
Hi,
in GCC 8 we changed -fprofile-generate= to use mangled absolute paths in
the directory. This was necessary to avoid clashes of files when gcc is
executed from different directories to build different sources of same
filename.
However this made it diffic
Hi,
This patch fixes an ICE we were seeing due to a missing vec_duplicate
pattern.
Regression tested on arm-none-eabi.
Is this OK for trunk?
gcc/ChangeLog:
2020-04-15 Andre Vieira
* config/arm/mve.md (mve_vec_duplicate): New pattern.
(V_sz_elem2): Remove unused mode attri
> -Original Message-
> From: Andre Vieira (lists)
> Sent: 15 April 2020 08:43
> To: gcc-patches@gcc.gnu.org
> Cc: Kyrylo Tkachov
> Subject: [PATCH][GCC][Arm]: MVE: Add mve vec_duplicate pattern
>
> Hi,
>
> This patch fixes an ICE we were seeing due to a missing vec_duplicate
> pattern
Hi!
This change started with a bugreport about a typo in one requires testcase
(diagnosed with -Wunknown-pragmas only), but following discussion lead to
noting that we do not diagnose restriction that requires directives in
C/C++ may only appear at file or namespace scope; and several our tests
vi
Hi!
This snippet has been copied from the non-structured binding declaration
parsing later in the function, and while for non-structured bindings
it can be followed by comma or semicolon, structured bindings may be
only followed by semicolon.
Fixed thusly, bootstrapped/regtested on x86_64-linux a
Hi Jakub,
> -Original Message-
> From: Jakub Jelinek
> Sent: 15 April 2020 08:28
> To: Richard Earnshaw ; Richard Sandiford
> ; Kyrylo Tkachov ;
> Richard Henderson
> Cc: gcc-patches@gcc.gnu.org
> Subject: [PATCH] aarch64: Fix bootstrap with old binutils [PR93053]
>
> Hi!
>
> As report
On Wed, Apr 15, 2020 at 08:27:43AM +, Kyrylo Tkachov wrote:
> > I've been testing this in distro scratch builds, so I don't really have
> > there the old assembler, but bootstrapped/regtested 5 times, for each of the
> > two patches once as is and once with s/cas/caszz/ in the configure{.ac,} t
Hi all,
Second version of this addressing comments.
Bootstraped on aarch64 and regressioned. Okay for trunk?
Andrea
gcc/ChangeLog
2020-??-?? Andrea Corallo
* config/aarch64/falkor-tag-collision-avoidance.c
(valid_src_p): Check for aarch64_address_info type before
a
From: Xionghu Luo
This "subtract/extend/add" existed for a long time and still annoying us
(PR37451, PR61837) when converting from 32bits to 64bits, as the ctr
register is used as 64bits on powerpc64, Andraw Pinski had a patch but
caused some issue and reverted by Joseph S. Myers(PR37451, PR37782
Hi Rasmus,
Thanks for your proposal.
This is an issue we discussed a bit very recently
https://gcc.gnu.org/pipermail/gcc-patches/2020-April/543073.html
and it's nice to see a proposal not requiring
the replication of all the link spec logic.
I had mixed feelings about a change to get gcc -r be
luoxhu--- via Gcc-patches writes:
> From: Xionghu Luo
>
> This "subtract/extend/add" existed for a long time and still annoying us
> (PR37451, PR61837) when converting from 32bits to 64bits, as the ctr
> register is used as 64bits on powerpc64, Andraw Pinski had a patch but
> caused some issue an
On Wed, Apr 15, 2020 at 03:47:55AM -0500, luoxhu--- via Gcc-patches wrote:
> 2020-04-15 Xiong Hu Luo
>
> PR rtl-optimization/37451, PR target/61837
> loop-doloop.c (doloop_modify): Simplify (add -1; zero_ext; add +1)
"* " missing before loop-doloop.c
> to zero_ext.
> -
On 15/04/2020 10.52, Olivier Hainque wrote:
> Hi Rasmus,
>
> Thanks for your proposal.
>
> This is an issue we discussed a bit very recently
> https://gcc.gnu.org/pipermail/gcc-patches/2020-April/543073.html
>
> and it's nice to see a proposal not requiring
> the replication of all the link spec
Ping.
On 04/04/2020 13:33, Iain Buclaw wrote:
> Hi,
>
> Some small improvements and clarifications have been done in the D ABI
> specification to remove all ambiguities found in the current grammar,
> this implementation now more closely resembles the spec, whilst
> maintaining compatibility with
Without disabling this, the pattern can try and move DImode values
between floating point registers and general registers.
The constraints on this pattern can't handle that, and reload goes into
an infinite loop.
This was the cause of a testsuite failure in cde_v_1_mve.c, which is now
gone.
A DIm
Hi Fritz,
I wonder: could you simply replace the gfc_error_opt(0, ...) call with
gfc_error?
Yes. Looking back at the code, I think it can also be cleaned up
a little - turning the error to warnings is only needed on that
particular branch, and resetting it to the default can also
happen there
On 4/15/20 12:26 PM, Thomas Koenig via Fortran wrote:
+ /* Turn erros into warnings with -std=gnu and -std=legacy,
Only glanced at it – but can you also fix the old* typo "erro(r)s"?
Tobias
(*old as the comment block has been moved around)
-
Mentor Graphics (Deutschland
Am 15.04.20 um 12:33 schrieb Tobias Burnus:
On 4/15/20 12:26 PM, Thomas Koenig via Fortran wrote:
+ /* Turn erros into warnings with -std=gnu and -std=legacy,
Only glanced at it – but can you also fix the old* typo "erro(r)s"?
Yes, I think I can manage that :-)
Regards
Thomas
> -Original Message-
> From: Matthew Malcomson
> Sent: 15 April 2020 11:23
> To: gcc-patches@gcc.gnu.org
> Cc: Kyrylo Tkachov ; Ramana Radhakrishnan
> ; Richard Earnshaw
> ; nd
> Subject: [Arm] Disallow arm_movdi when targetting MVE
>
> Without disabling this, the pattern can try and
Hi Andrea,
> -Original Message-
> From: Andrea Corallo
> Sent: 15 April 2020 09:47
> To: Kyrylo Tkachov
> Cc: nd ; gcc-patches@gcc.gnu.org
> Subject: Re: [PATCH V2]aarch64: falkor-tag-collision-avoidance.c fix
> valid_src_p for use of uninitialized value
>
> Hi all,
>
> Second version
This adds the SSA name version to the gdb pretty-printing of SSA names.
(gdb) p (tree)$1
$5 =
Tested (see above...).
OK?
Thanks,
Richard.
2020-04-15 Richard Biener
* gdbhooks.py (TreePrinter): Print SSA_NAME_VERSION of SSA_NAME
nodes.
---
gcc/gdbhooks.py | 3 +++
1 file
Thank you for your suggestions.
I have modified accordingly and a full test has been carried, no new failure
witnessed.
Attached please find the new patch which has been adjusted to be suitable for
git am.
Does the v2 patch look better ?
Thanks,
Duan bo
-Original Message-
From: Wilco
Kyrylo Tkachov writes:
> Hi Andrea,
>
>> -Original Message-
>> From: Andrea Corallo
>> Sent: 15 April 2020 09:47
>> To: Kyrylo Tkachov
>> Cc: nd ; gcc-patches@gcc.gnu.org
>> Subject: Re: [PATCH V2]aarch64: falkor-tag-collision-avoidance.c fix
>> valid_src_p for use of uninitialized valu
On 13/04/2020 21:40, Wilco Dijkstra wrote:
> Hi Duanbo,
>
>> This is a simple fix for pr94577.
>> The option -mabi=ilp32 should not be used in large code model. Like x86,
>> using -mx32 and -mcmodel=large together will result in an error message.
>> On aarch64, there is no error message for this
On Tue, Apr 07, 2020 at 11:12:48PM -0400, Gustavo Romero via Gcc-patches wrote:
> Currently an use of get() method of dump_context singleton in optinfo
> framework causes a new class to be instantiated and when its dtor
> is called it calls delete on uninitialized data, causing an ICE.
To be preci
On Wed, 2020-04-15 at 14:52 +0200, Richard Biener wrote:
> This adds the SSA name version to the gdb pretty-printing of SSA
> names.
>
> (gdb) p (tree)$1
> $5 =
>
> Tested (see above...).
>
> OK?
> Thanks,
> Richard.
>
> 2020-04-15 Richard Biener
>
> * gdbhooks.py (TreePrinter): Pri
2020-04-15 Uroš Bizjak
PR target/94603
* config/i386/i386-builtin.def (__builtin_ia32_movq128):
Require OPTION_MASK_ISA_SSE2.
testsuite/ChangeLog:
2020-04-15 Uroš Bizjak
PR target/94603
* gcc.target/i386/pr94603.c: New test.
Bootstrapped and regression tested on x86_64-linux-gnu {,-m32}.
Iain Buclaw via Gcc-patches writes:
> Hi,
>
> This patch adds an effect target d_runtime_has_std_library to
> target-supports.exp, and some preliminary uses of it.
>
> The current check_effective_target_d_runtime procedure returns false if
> the target is without any core runtime library for D. T
On Tue, 2020-04-14 at 17:26 +0200, Sebastian Huber wrote:
> Hello Jeff,
>
> On 08/04/2020 22:24, Jeff Law wrote:
>
> > On Wed, 2020-04-08 at 19:47 +0200, Sebastian Huber wrote:
> > > Add a start/end file specification if the -qrtems option is present.
> > > Allow targets to customize it.
> > >
>
Hi Richard,
> Iain Buclaw via Gcc-patches writes:
>> Hi,
>>
>> This patch adds an effect target d_runtime_has_std_library to
>> target-supports.exp, and some preliminary uses of it.
>>
>> The current check_effective_target_d_runtime procedure returns false if
>> the target is without any core run
Hi,
get_ref_base_and_extent recognizes ARRAY_REFs with variable index but
into arrays of length one as constant offset accesses. However,
max_size in such cases is extended to span the whole element. This
confuses SRA verification when SRA also builds its (total
scalarization) access structures
> Yes. Looking back at the code, I think it can also be cleaned up
> a little - turning the error to warnings is only needed on that
> particular branch, and resetting it to the default can also
> happen there, and at the target of a goto statement.
>
> So, here's an updated patch. OK for trunk?
On Tue, Apr 14, 2020 at 7:54 AM Linus König wrote:
>
> Hi all,
>
> the PR has just recently been committed. Paul gave his offline approval.
> I only realized recently, that the NULL pointer check can actually be
> ommitted if the check is moved in the code. In the commit however, it is
> still rig
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 4/9/20 1:32 PM, Jason Merrill wrote:
On 4/9/20 3:24 PM, Martin Sebor wrote:
On 4/9/20 1:03 PM, Jason Merrill wrote:
On 4/8/20 1
Hi Fritz,
While you're touching the code anyway, how would you feel about
replacing the nearby "goto done"s with a chain of "else if"? There's
really no reason I can see for goto here, since the block following
the conditions is already "done".
I think this would really be pushing things at st
On Wed, 15 Apr 2020, Martin Jambor wrote:
> Hi,
>
> get_ref_base_and_extent recognizes ARRAY_REFs with variable index but
> into arrays of length one as constant offset accesses. However,
> max_size in such cases is extended to span the whole element.
You mean f[d] gets offset zero and max_size
On Wed, Apr 15, 2020 at 1:47 PM Thomas Koenig wrote:
>
> Hi Fritz,
>
> > While you're touching the code anyway, how would you feel about
> > replacing the nearby "goto done"s with a chain of "else if"? There's
> > really no reason I can see for goto here, since the block following
> > the conditio
Another C++20 change from P1614R2, "The Mothership has Landed".
* include/std/typeindex (operator<=>): Define for C++20.
* testsuite/20_util/typeindex/comparison_operators_c++20.cc: New test.
Tested powerpc64le-linux, committed to master.
commit 4714fd14afadbfdab0cc76a8b3fdf7a81
Some more C++20 changes from P1614R2, "The Mothership has Landed".
This removes all redundant equality and inequality operators in the
Utilities clause, as they can be synthesized from the remaining equality
operators.
It also removes the single redundant operator in the Localization
clause, beca
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 4/9/20 1:32 PM, Jason Merrill wrote:
> > > > > >
Here we're ICE'ing in do_narrow during error-recovery, because ocp_convert
returns error_mark_node after it attempts to reduce a const decl to its
erroneous DECL_INITIAL via scalar_constant_value, and we later pass this
error_mark_node to fold_build2 which isn't prepared to handle error_mark_nodes.
This patch to the Go frontend marks builtin_prefetch as novops. This
corresponds to how it is defined in builtins.def. This fixes GCC PR
94607. Bootstrapped and ran Go testsuite on x86_64-pc-linux-gnu.
Committed to mainline.
Ian
2020-04-15 Ian Lance Taylor
PR go/94607
* go-gcc.cc (class Gc
Some more C++20 changes from P1614R2, "The Mothership has Landed".
* include/bits/fs_dir.h (file_status): Define operator== for C++20.
(directory_entry): Define operator<=> and remove redundant comparison
operators for C++20.
* include/bits/fs_fwd.h (space_info): De
On 15/04/2020 17:17, Richard Sandiford wrote:
> Iain Buclaw via Gcc-patches writes:
>> Hi,
>>
>> This patch adds an effect target d_runtime_has_std_library to
>> target-supports.exp, and some preliminary uses of it.
>>
>> The current check_effective_target_d_runtime procedure returns false if
>
Hello David-
I would appreciate hearing your thoughts please on the following
(relatively minor) issue... There is a little bug with colorization in
diagnostics: in case a location only points to the first byte of a
multibyte sequence, the colorization produces corrupted output as it
interrupts th
Ping.
We need this patch for our product building.
thanks.
Qing
> Begin forwarded message:
>
> From: Qing Zhao via Gcc-patches
> Subject: PING [PATCH][gcc][PR94230]provide an option to change the size
> limitation for -Wmisleading-indent
> Date: April 8, 2020 at 2:39:22 PM CDT
> To: dmalc..
Oops, consider the typo in the subject line fixed. Also ...
On Wed, 15 Apr 2020, Patrick Palka wrote:
> Here we're ICE'ing in do_narrow during error-recovery, because ocp_convert
> returns error_mark_node after it attempts to reduce a const decl to its
> erroneous DECL_INITIAL via scalar_constan
Hi Jiufu,
Just reviewing random things as I see them...
On Wed, Apr 15, 2020 at 09:56:00AM +0800, Jiufu Guo wrote:
> This patch only supports simple loops: one exit edge with one major basic
> block.
That is fine for a proof-of-concept, but will need fixing perhaps.
> --- a/gcc/common.opt
> ++
Hi!
On Wed, Apr 15, 2020 at 08:21:03AM +0200, Richard Biener wrote:
> On Wed, Apr 15, 2020 at 3:56 AM Jiufu Guo via Gcc-patches
> wrote:
> > As you may know, we have loop unroll pass in RTL which was introduced a few
> > years ago, and works for a long time. Currently, this unroller is using the
This libgo patch by Eric Fang fixes the Aarch64 implementation of
aeshashbody to use all 64 bits of the hash seed. This is the gccgo
fix for https://golang.org/issue/33960. Committed to mainline.
Ian
4312e0f1391133d6bcd617bb5a81c7caaf6faf99
diff --git a/gcc/go/gofrontend/MERGE b/gcc/go/gofronten
On 4/15/20 4:12 AM, Jakub Jelinek wrote:
Hi!
This snippet has been copied from the non-structured binding declaration
parsing later in the function, and while for non-structured bindings
it can be followed by comma or semicolon, structured bindings may be
only followed by semicolon.
Fixed thusl
On 4/15/20 4:43 PM, Patrick Palka wrote:
Oops, consider the typo in the subject line fixed. Also ...
On Wed, 15 Apr 2020, Patrick Palka wrote:
Here we're ICE'ing in do_narrow during error-recovery, because ocp_convert
returns error_mark_node after it attempts to reduce a const decl to its
err
Fix regression caused by PR target/93932 backport.
When I back ported the fix for PR target/93932 to the GCC 9 branch, I put in an
unintended regression when the GCC compiler is optimizing the vec_extract
built-in function, and the vector element is in memory, and the index is
variable. This patc
on 2020/4/15 下午2:21, Richard Biener via Gcc-patches wrote:
> On Wed, Apr 15, 2020 at 3:56 AM Jiufu Guo via Gcc-patches
> wrote:
>>
>> Hi,
>>
>> As you may know, we have loop unroll pass in RTL which was introduced a few
>> years ago, and works for a long time. Currently, this unroller is using th
Segher Boessenkool writes:
Hi,
Thanks for all your comments!
> Hi!
>
> On Wed, Apr 15, 2020 at 08:21:03AM +0200, Richard Biener wrote:
>> On Wed, Apr 15, 2020 at 3:56 AM Jiufu Guo via Gcc-patches
>> wrote:
>> > As you may know, we have loop unroll pass in RTL which was introduced a few
>> > ye
Segher Boessenkool writes:
> Hi Jiufu,
>
> Just reviewing random things as I see them...
>
> On Wed, Apr 15, 2020 at 09:56:00AM +0800, Jiufu Guo wrote:
>> This patch only supports simple loops: one exit edge with one major basic
>> block.
>
> That is fine for a proof-of-concept, but will need fi
Hi!
bison 3 apparently made a backwards incompatible change, dropped
YYLEX_PARAM/YYPARSE_PARAM support and instead needs %param or %lex-param
and %parse-param. Furthermore, there is no easy way to conditionalize
on bison version in the *.y files.
While e.g. glibc bumped bison requirement and just
59 matches
Mail list logo
