On Sat, 14 Mar 2020, Jakub Jelinek wrote:
> Hi!
>
> On the following testcase, if there is ASLR, the compiler generates
> different code each time (out of 1000 invocations 994 unique assembler
> contents). The problem is that undistribute_bitref_for_vector uses
> a hash_map from a tree (SSA_NAME
On Sat, 14 Mar 2020, Jakub Jelinek wrote:
> Hi!
>
> The following testcase fails with -fcompare-debug. The problem is that
> bar is marked as address_taken only with -g and not without.
> I've tracked it down to insert_init_stmt calling gimple_regimplify_operands
> even on DEBUG_STMTs. That fun
Hi!
The recent match.pd changes can generate a MEM_REF which can be seen by the
C FE folding routines. Unlike the C++ FE, they weren't expected in the C FE
yet. MEM_REF should be handled like INDIRECT_REF, except that it has two
operands rather than just one and that we should preserve the type
Hi.
It's fix for Darwin target and similar others which do
not support the asembler directive.
Ready for master?
Thanks,
Martin
gcc/testsuite/ChangeLog:
2020-03-16 Martin Liska
PR lto/94157
* gcc.dg/lto/pr94157_0.c: Add wa_noexecstack effective
target filter.
Hi Martin,
> It's fix for Darwin target and similar others which do
> not support the asembler directive.
>
> Ready for master?
I'm usually all for using effective-target keywords instead of ad-hoc
tests or target lists, but this seems like a single-use case and thus a
bit too much. Maybe restri
On Wed, Mar 11, 2020 at 5:07 PM Iain Sandoe wrote:
>
> Bin.Cheng wrote:
>
> > On Thu, Mar 5, 2020 at 10:18 PM Iain Sandoe wrote:
>
> >> With current trunk + Bin’s two approved patches.
> >>
> >> I see no change in the testcase (lambda-09-capture-object.C) before / after
> >> the patch
> >> (it
On 3/16/20 9:48 AM, Rainer Orth wrote:
Hi Martin,
It's fix for Darwin target and similar others which do
not support the asembler directive.
Ready for master?
I'm usually all for using effective-target keywords instead of ad-hoc
tests or target lists, but this seems like a single-use case an
Hi,
This patch merges the D front-end implementation with upstream dmd
b061bd744.
Fixes an ICE in the parser, and deprecates a previously allowed style of
syntax that deviated from GNU-style extended asm.
Bootstrapped and tested on x86_64-linux-gnu, and committed to trunk.
Regards
Iain.
---
g
Hi,
This patch merges the libphobos implementation with upstream druntime
6c45dd3a, and phobos 68cc18adb.
This change surrounds the gcc-style asm operands with parentheses, as
the old style of optionally omitting is now deprecated.
This is being applied first before the changes to the compiler t
Hi Martin,
>>> gcc/testsuite/ChangeLog:
>>>
>>> 2020-03-16 Martin Liska
>>>
>>> PR lto/94157
>>> * gcc.dg/lto/pr94157_0.c: Add wa_noexecstack effective
>>> target filter.
>>> * lib/target-supports.exp: Add
>>> check_effective_target_wa_noexecstack.
>> One question (because I
On 3/16/20 11:07 AM, Rainer Orth wrote:
Minus the quoting, it's only 59 chars long...
Ah ok. I will make better next time ;)
Martin
Hi Kyrill,
> This is ok but please bootstrap it on arm-none-linux-gnueabihf as well.
I have bootstrapped this patch on arm-none-linux-gnueabihf and found no issues.
There is problem with git commit rights, could you commit this patch on my
behalf.
Regards
SRI
Fr
Hi Kyrill,
> Ok, but make sure it bootstraps on arm-none-linux-gnueabihf (as with the
other patches in this series)
I have bootstrapped this patch on arm-none-linux-gnueabihf and found no issues.
There is problem with git commit rights, could you commit this patch on my
behalf.
Regards
SRI.
__
On Thu, Mar 12, 2020 at 7:54 AM Martin Liška wrote:
>
> Hi.
>
> There's updated version of the patch.
> Changes from the previous version:
> - comment added to ld_plugin_symbol
> - new section renamed to ext_symtab
> - assert added for loop iterations in produce_symtab and
> produce_symtab_extens
On 13/03/20 20:38 +0100, Uros Bizjak via Libstdc++ wrote:
x32 does not support MS ABI, skip testcases that require it.
2020-03-13 Uroš Bizjak
* testsuite/20_util/bind/91371.cc: Skip for x32.
* testsuite/20_util/is_function/91371.cc: Ditto.
* testsuite/20_util/is_member_function_poin
Hello Kyrill,
Following patch is the rebased version of v1.
(version v1) https://gcc.gnu.org/pipermail/gcc-patches/2019-November/534358.html
Hello,
This patch supports following MVE ACLE intrinsics with ternary operands.
vabavq_s8, vabavq_s16, vabavq_s32, vbicq_m_n_s16, vbicq_m_n_s32,
vbi
Hello Kyrill,
Following patch is the rebased version of v1.
(version v1) https://gcc.gnu.org/pipermail/gcc-patches/2019-November/534355.html
Hello,
This patch supports following MVE ACLE intrinsics with ternary operands.
vpselq_u8, vpselq_s8, vrev64q_m_u8, vqrdmlashq_n_u8, vqrdmlahq_n_u8,
Hello Kyrill,
Following patch is the rebased version of v1.
(version v1) https://gcc.gnu.org/pipermail/gcc-patches/2019-November/534322.html
Hello,
This patch supports following MVE ACLE intrinsics with ternary operands.
vrmlaldavhaxq_s32, vrmlsldavhaq_s32, vrmlsldavhaxq_s32, vaddlvaq_p_s
Hi Kyrill,
I have re-based this patch, please commit the following patch on my behalf.
https://gcc.gnu.org/pipermail/gcc-patches/2020-March/541826.html
Regards,
SRI.
From: Gcc-patches on behalf of Srinath
Parvathaneni
Sent: 16 March 2020 10:54
To: Kyrill Tkacho
This is a part of a WIP series doing vectorizer rework. To be committed
when stage1 opens.
This removes the SLP_INSTANCE_GROUP_SIZE member since the number of
lanes throughout a SLP subgraph is not necessarily constant.
* tree-vectorizer.h (SLP_INSTANCE_GROUP_SIZE): Remove.
(_s
This is a part of a WIP series doing vectorizer rework. To be committed
when stage1 opens.
This delays the SLP permutation check to vectorizable_load and optimizes
permutations only after all SLP instances have been generated and the
vectorization factor is determined.
2020-02-24 Richard Bien
Dear Sir/Madam,
We are offer custom sportswear with 5PC MOQ, and wicking fabric
Digital printing , Embroidery printing and screen printing is ok .
Sample first is ok ,and paypal payment,
Sample time 7 days . 1000 pcs production time is 15 day
Wish your soon reply
Elvis lau
On 3/16/20 1:16 PM, Richard Biener wrote:
This is a part of a WIP series doing vectorizer rework. To be committed
when stage1 opens.
Hi.
Have you considered publishing a public git branch where you will maintain
the suggested vectorization patches?
Thanks,
Martin
On Mon, 16 Mar 2020, Martin Liška wrote:
> On 3/16/20 1:16 PM, Richard Biener wrote:
> > This is a part of a WIP series doing vectorizer rework. To be committed
> > when stage1 opens.
>
> Hi.
>
> Have you considered publishing a public git branch where you will maintain
> the suggested vectoriz
On 3/16/20 12:12 PM, H.J. Lu wrote:
(enum ld_plugin_tag): Add LDPT_GET_SYMBOLS_V and
^^^ Typo,
Thank you. I fixed that in my development branch.
Martin
On 3/16/20 2:49 PM, Richard Biener wrote:
If folks think this is useful I can do that (but expect it to see
rebases frequently).
Frequent rebasing is fine to me.
Martin
On Mon, Mar 16, 2020 at 6:50 AM Martin Liška wrote:
>
> On 3/16/20 12:12 PM, H.J. Lu wrote:
> > (enum ld_plugin_tag): Add LDPT_GET_SYMBOLS_V and
> > ^^^ Typo,
>
> Thank you. I fixed that in my development branch.
Still not right. It should
On 3/16/20 3:34 PM, H.J. Lu wrote:
It is LDPT_ADD_SYMBOLS_V2, not LDPT_GET_SYMBOLS_V2.
Sorry. It's fixed now.
Martin
Hi Martin,
On Sun, 15 Mar 2020, Martin Sebor wrote:
> On 3/11/20 4:18 PM, Patrick Palka via Gcc-patches wrote:
> ...
> > Hmm, like this? This version introduces a new static member function
> > diagnosing_failed_constraint::replay_errors_p that checks
> > current_constraint_diagnosis_depth, and
Now that convert_like creates an IMPLICIT_CONV_EXPR when it converts
something that involves a class in a template, we must be prepared to
handle it. In this test, we have a class S and we're converting it
to long int& using a user-defined conversion since we're performing
-- on it. So cp_build_u
On Mon, 16 Mar 2020, Martin Liška wrote:
> On 3/16/20 2:49 PM, Richard Biener wrote:
> > If folks think this is useful I can do that (but expect it to see
> > rebases frequently).
>
> Frequent rebasing is fine to me.
refs/users/rguenth/heads/slp-reorg
Richard.
Hi!
I'd like to ping the
https://gcc.gnu.org/ml/gcc-patches/2020-March/541542.html
P2 PR91993 patch
If you think it is too dangerous for GCC10 and should be postponed,
I can ping it after 10.1 is released, or e.g. if you think for GCC10
we should for all codes handle that way only orig_op0 an
Hi,
This patch resets the libphobos soversion. Firstly, because Phobos,
being template heavy, makes no attempt at being backwards compatible
with previous versions. Even improvements in attribute inference in the
compiler can have the effect of changing the mangling of many symbols,
which is wha
Hello Kyrill,
> What is the point of repeating the scan-assembler directives here? The
> first scan-assembler should be redundant given the scan-assembler-times ?
> Otherwise ok.
In this patch testcases are modified by removing the redundant
scan-assembler directive.
Please commit to trunk on m
Ping: https://gcc.gnu.org/pipermail/gcc-patches/2020-March/541521.html
On 3/4/20 2:06 PM, Martin Sebor wrote:
A 2017 change that propagated call location to GIMPLE statements
had the unexpected (though not incorrect) effect of setting
the location on calls to __builtin_alloca. When such calls a
In this PR, we are performing constexpr evaluation of a CONSTRUCTOR of type
union U which looks like
{.a=foo (&)}.
Since the function foo takes a reference to the CONSTRUCTOR we're building, it
could potentially modify the CONSTRUCTOR from under us. In particular since U
is a union, the evalua
Hi Srinath,
I've pushed the first three of the patches for you to master:
[ARM][GCC][3/x]: MVE ACLE intrinsics framework patch.
[ARM][GCC][2/x]: MVE ACLE intrinsics framework patch.
[ARM][GCC][1/x]: MVE ACLE intrinsics framework patch.
For this first one I adjusted the add_options directives for
Segher Boessenkool writes:
> On Fri, Mar 13, 2020 at 01:31:19PM +, Richard Sandiford wrote:
>> This might not be what you mean, but for:
>>
>> int
>> f1 (void)
>> {
>> int x = 1;
>> asm volatile ("": "=m" (x));
>> return x;
>> }
>>
>> struct s { int i[5]; };
>> struct s
>> f2 (void)
>>
On Mon, Mar 16, 2020 at 06:29:39AM +, Yangfei (Felix) wrote:
> Sorry for not getting your point here.
Trying 7 -> 8:
7: r99:SI=r103:SI>>0x8
REG_DEAD r103:SI
8: r100:SI=r99:SI&0x6
REG_DEAD r99:SI
Failed to match this instruction:
(set (reg:SI 100)
(and:SI (lshiftrt:SI (
Lewis Hyatt via Gcc-patches writes:
> Hello-
>
> Currently, if an option is both undocumented and an alias for a second option,
> the help text generated by gcc --help directs the reader to use the other
> option instead. This makes sense for deprecated options, but it seems this
> pattern is also
Christophe Lyon via Gcc-patches writes:
> On Wed, 11 Mar 2020 at 00:37, Joseph Myers wrote:
>>
>> On Tue, 10 Mar 2020, Christophe Lyon wrote:
>>
>> > sizeless-1.c and sizeless-2.c have the same code, but the latter is
>> > compiled with -msve-vector-bits=256 and expects different
>> > warnings/er
On Mon, Mar 16, 2020 at 05:47:03PM +, Richard Sandiford wrote:
> Segher Boessenkool writes:
> >> we do delete "x = 1" for f1. I think that's the expected behaviour.
> >> We don't yet delete the initialisation in f2, but I think in principle
> >> we could.
> >
> > Right. And this is incorrec
Segher Boessenkool writes:
> On Mon, Mar 16, 2020 at 05:47:03PM +, Richard Sandiford wrote:
>> Segher Boessenkool writes:
>> >> we do delete "x = 1" for f1. I think that's the expected behaviour.
>> >> We don't yet delete the initialisation in f2, but I think in principle
>> >> we could.
>>
Hi Adam,
Right now I am passing
"[http://raghavpa_...@primary-proxy.gslb.intranet.barcapint.com:8080]https://www2.1010data.com/cgi-bin/gw";
For gateway option
Should I change it to
"[http://raghavpa_...@primary-proxy.gslb.intranet.barcapint.com:8080]https://www2.1010data.com/cgi-bin/prime-lates
Attn; Email user,
We are pleased to announce that your "#e-mail#" was nominated as one of the 28
recipients under the Second category in the online DONATION SWEEPSTAKE 2020
Prospect as part of the Bill & Melinda Gates Foundation to relief Humanitarian
struggle.
For claims and clearance, kindly
On Mon, Mar 16, 2020 at 07:46:57PM +, Richard Sandiford wrote:
> > The write to "x" *before the asm* is deleted. I cannot think of any
> > interpretation where that is correct (this does not involve inline asm
> > at all: it is deleting an observable side effect before the exception).
>
> It'
The recent fix to avoid modifying in place the type argument in
handle_access_attribute (PR 92721) was incomplete and didn't fully
resolve the problem (an ICE in the C++ front-end). The attached
patch removes the remaining modification that causes the ICE. In
addition, the change adjusts checkin
The following committed patch solves
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94185
The patch was successfully bootstrapped and tested on x86-64.
On 3/16/20 4:41 PM, Martin Sebor wrote:
The recent fix to avoid modifying in place the type argument in
handle_access_attribute (PR 92721) was incomplete and didn't fully
resolve the problem (an ICE in the C++ front-end). The attached
patch removes the remaining modification that causes the ICE.
On 3/16/20 10:57 AM, Marek Polacek wrote:
Now that convert_like creates an IMPLICIT_CONV_EXPR when it converts
something that involves a class in a template, we must be prepared to
handle it. In this test, we have a class S and we're converting it
to long int& using a user-defined conversion sin
Tested on Linux-PPC64.
This ain't no regression. But it seems to hamper attempts to fix library
regressions (see https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94033).
2020-03-16 Ville Voutilainen
gcc/
PR c++/94197
* cp/method.c (assignable_expr, constructible_expr): Push
a def
On Mon, 2020-03-16 at 11:39 -0600, Martin Sebor via Gcc-patches wrote:
> Ping: https://gcc.gnu.org/pipermail/gcc-patches/2020-March/541521.html
I think Jakub indicated the test was incorrect. Please resolve that issue and
repost. I think the core patch is OK, so we just need to fixup the test.
j
On Mon, 2020-03-16 at 09:23 +0100, Jakub Jelinek via Gcc-patches wrote:
> Hi!
>
> The recent match.pd changes can generate a MEM_REF which can be seen by the
> C FE folding routines. Unlike the C++ FE, they weren't expected in the C FE
> yet. MEM_REF should be handled like INDIRECT_REF, except t
On 3/15/20 7:35 PM, Jakub Jelinek wrote:
On Sun, Mar 15, 2020 at 05:21:59PM -0400, Jason Merrill wrote:
Let's use temp_override.
So like this?
Yes, thanks.
Bootstrapped/regtested on x86_64-linux and i686-linux.
2020-03-15 Jakub Jelinek
PR c++/90995
* parser.c (cp_parse
Hi,
When generating thunks in the D front-end, they need not necesarily be
in the same compilation unit as the module where the target function is
declared. When this happens, don't make the thunk public. Later on
expand_thunk will be called with force_gimple_thunk=true, so the thunk
can never b
On Mon, Mar 16, 2020 at 06:11:08PM +, Richard Sandiford wrote:
> Lewis Hyatt via Gcc-patches writes:
...
> > FWIW there are three other options currently affected by this change
> > (-Wimplicit-fallthrough, -fcf-protection, and -flive-patching). The change
> > for
> > -Wimplicit-fallthrough I
On Mon, 16 Mar 2020 at 23:25, Ville Voutilainen
wrote:
>
> Tested on Linux-PPC64.
>
> This ain't no regression. But it seems to hamper attempts to fix library
> regressions (see https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94033).
It occurred to me that this can be done in one place.
2020-03-17
On Mon, Mar 16, 2020 at 6:11 PM Lewis Hyatt wrote:
> Regarding -Wmissing-format-attribute, that is an interesting case, it's the
> only
> instance in any *.opt that has an = sign in the Alias target. If I understand
> correctly, this one can't use the 3-argument form of Alias() because
> -Wno-mis
The service_already_exists exception type specified in the TS doesn't
have any constructors defined. Since its base class isn't default
constructible, that means has no usable constructors. This may be a
defect in the TS.
This patch fixes it by adding a default constructor, but making it
private.
On 3/16/20 6:13 PM, Ville Voutilainen wrote:
On Mon, 16 Mar 2020 at 23:25, Ville Voutilainen
wrote:
Tested on Linux-PPC64.
This ain't no regression. But it seems to hamper attempts to fix library
regressions (see https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94033).
It occurred to me that th
Hi,
This patch fixes a logic bug in the adjustment of nested fields in
anonymous aggregates in the D front-end, closing PR d/92309.
Bootstrapped and tested on x86_64-linux-gnu, and committed to trunk.
Regards
Iain.
---
gcc/d/ChangeLog:
PR d/92309
* types.cc (fixup_anonymous_off
On 3/16/20 3:41 PM, Jeff Law wrote:
On Mon, 2020-03-16 at 11:39 -0600, Martin Sebor via Gcc-patches wrote:
Ping: https://gcc.gnu.org/pipermail/gcc-patches/2020-March/541521.html
I think Jakub indicated the test was incorrect. Please resolve that issue and
repost. I think the core patch is OK,
On Mon, Mar 16, 2020 at 05:12:15PM -0400, Jason Merrill wrote:
> On 3/16/20 10:57 AM, Marek Polacek wrote:
> > Now that convert_like creates an IMPLICIT_CONV_EXPR when it converts
> > something that involves a class in a template, we must be prepared to
> > handle it. In this test, we have a class
Hi,
> -Original Message-
> From: Segher Boessenkool [mailto:seg...@kernel.crashing.org]
> Sent: Tuesday, March 17, 2020 1:58 AM
> To: Yangfei (Felix)
> Cc: gcc-patches@gcc.gnu.org; Zhanghaijian (A)
> Subject: Re: [PATCH PR94026] combine missed opportunity to simplify
> comparisons with z
Hi
The testcase pr78255.c triggers ice when testing GCC trunk on aarch64 with
-mabi=ilp32 -fPIC.
Case path: gcc/testsuite/gcc.target/aarch64/pr78255.c
The ICE is caused by insufficient support for the tiny code model under ilp32
mode with fPIC option, where a SI mode register might be used for
65 matches
Mail list logo
