On 7/9/21 6:14 PM, Peter Bergner wrote:
> ...code section. Does this look better? I'm currently running bootstraps
> and regtests on LE and BE.
Bootstrap and regtesting on both LE and BE showed no regressions.
Peter
On Thu, Jul 8, 2021 at 11:16 PM Richard Biener
wrote:
>
> On Thu, Jul 8, 2021 at 8:02 PM Martin Sebor via Gcc-patches
> wrote:
> >
> > Hi Ian,
> >
> > Yesterday's enhancement to -Warray-bounds has exposed a couple of
> > issues in libgo where the code writes into an invalid constant
> > address
Hi Richard,
on 2021/7/8 下午8:38, Richard Sandiford via Gcc-patches wrote:
> Quoting from the final patch in the series:
>
>
> This patch adds support for reusing a main loop's reduction accumulator
> in an epilogue loop.
On 7/8/21 8:26 PM, Peter Bergner wrote:
> We do need different code for LE versus BE. So you want something like
>
> if (WORDS_BIG_ENDIAN) {...} else {...}
>
> ...instead? I can try that to see if the code is easier to read.
[snip]
> Let me make the changes you want and I'll repost with what
The attached tweak avoids the new -Warray-bounds instances when
building libatomic for arm. Christophe confirms it resolves
the problem (thank you!)
As we have discussed, the main goal of this class of warnings
is to detect accesses at addresses derived from null pointers
(e.g., to struct
On Fri, 9 Jul 2021, Jason Merrill wrote:
> On 7/9/21 4:18 PM, Patrick Palka wrote:
> > On Fri, 9 Jul 2021, Patrick Palka wrote:
> >
> > > On Fri, 9 Jul 2021, Jason Merrill wrote:
> > >
> > > > On 7/9/21 3:18 PM, Patrick Palka wrote:
> > > > > This adds support for declaring (class-scope)
On 7/9/21 2:18 PM, Iain Sandoe wrote:
Hi,
The mechanism used to date for uniquing the coroutine helper
functions (actor, destroy) was over-complicating things and
leading to the noted PR and also difficulties in setting
breakpoints on these functions (so this will help PR99215 as
well). The
On 7/9/21 4:18 PM, Patrick Palka wrote:
On Fri, 9 Jul 2021, Patrick Palka wrote:
On Fri, 9 Jul 2021, Jason Merrill wrote:
On 7/9/21 3:18 PM, Patrick Palka wrote:
This adds support for declaring (class-scope) deduction guides for a
member class template. Fortunately it seems only a couple
Created this patch to add GCC version to the graph data
for the options:
-fdump-rtl-all-graph
-fdump-tree-all-graph
-fdump-ipq-all-graph
-fcallgraph-info
-fdump-analyzer-callgraph
-fdump-analyzer-exploded-graph
-fdump-analyzer-supergraph
-fdump-analyzer-state-purge
-fdump-analyzer-feasibility
On Fri, Jul 09, 2021 at 04:18:34PM -0400, Patrick Palka via Gcc-patches wrote:
> > > > --- a/gcc/cp/name-lookup.c
> > > > +++ b/gcc/cp/name-lookup.c
> > > > @@ -7110,9 +7110,14 @@ lookup_qualified_name (tree scope, tree name,
> > > > LOOK_want want, bool complain)
> > > > else if (cxx_dialect
On Fri, 9 Jul 2021, Patrick Palka wrote:
> On Fri, 9 Jul 2021, Jason Merrill wrote:
>
> > On 7/9/21 3:18 PM, Patrick Palka wrote:
> > > This adds support for declaring (class-scope) deduction guides for a
> > > member class template. Fortunately it seems only a couple of changes
> > > are
duplicate_decls was not recognizing the explicit specialization as matching
the implicit specialization of g because
function_requirements_equivalent_p was seeing the C constraint on the
implicit one and not on the explicit.
I think that the usefulness of much of the concepts TS support is
On Fri, 9 Jul 2021, Jason Merrill wrote:
> On 7/9/21 3:18 PM, Patrick Palka wrote:
> > This adds support for declaring (class-scope) deduction guides for a
> > member class template. Fortunately it seems only a couple of changes
> > are needed in order for the existing CTAD machinery to handle
From: Andrew Pinski
Instead of waiting for DCE to remove the unused statement,
and maybe optimize another conditional, it is better if
we don't move the statement and have the statement
removed.
OK? Bootstrapped and tested on x86_64-linux-gnu.
Changes from v1:
* v2: Change the order of
On 7/9/21 3:01 PM, Patrick Palka wrote:
Here we're failing to treat 'new T[N]' as erroneous in a SFINAE context
when T isn't default constructible because expand_aggr_init_1 doesn't
communicate to build_aggr_init (its only SFINAE caller) whether the
initialization was actually successful. To
On 7/9/21 3:18 PM, Patrick Palka wrote:
This adds support for declaring (class-scope) deduction guides for a
member class template. Fortunately it seems only a couple of changes
are needed in order for the existing CTAD machinery to handle them like
any other deduction guide: we need to make
On 7/9/21 7:19 AM, Maxim Kuvyrkov wrote:
On 9 Jul 2021, at 09:16, Richard Biener via Gcc-patches
wrote:
On Thu, Jul 8, 2021 at 8:02 PM Martin Sebor via Gcc-patches
wrote:
Hi Ian,
Yesterday's enhancement to -Warray-bounds has exposed a couple of
issues in libgo where the code writes into
On Thu, 2021-06-17 at 10:18 -0500, Bill Schmidt via Gcc-patches wrote:
> 2021-06-07 Bill Schmidt
>
> gcc/
> * config/rs6000/rs6000-gen-builtins.c (consume_whitespace): New
> function.
> (advance_line): Likewise.
> (safe_inc_pos): Likewise.
> (match_identifier):
This adds support for declaring (class-scope) deduction guides for a
member class template. Fortunately it seems only a couple of changes
are needed in order for the existing CTAD machinery to handle them like
any other deduction guide: we need to make sure to give them a
FUNCTION_TYPE instead of
Here we're failing to treat 'new T[N]' as erroneous in a SFINAE context
when T isn't default constructible because expand_aggr_init_1 doesn't
communicate to build_aggr_init (its only SFINAE caller) whether the
initialization was actually successful. To fix this, this patch makes
Hi,
> On Jul 9, 2021, at 11:18 AM, Martin Jambor wrote:
>>
>>> On Jul 8, 2021, at 8:29 AM, Martin Jambor wrote:
diff --git a/gcc/tree-sra.c b/gcc/tree-sra.c
index c05d22f3e8f1..35051d7c6b96 100644
--- a/gcc/tree-sra.c
+++ b/gcc/tree-sra.c
@@ -384,6 +384,13 @@ static
On Wed, 2021-06-30 at 09:44 +0800, Xionghu Luo via Gcc-patches wrote:
> Gentle ping ^2, thanks.
>
> https://gcc.gnu.org/pipermail/gcc-patches/2021-April/568143.html
>
>
> On 2021/5/14 15:13, Xionghu Luo via Gcc-patches wrote:
> > Test SPEC2017 Ofast P8LE for this patch : 511.povray_r +1.14%,
>
Hi,
The mechanism used to date for uniquing the coroutine helper
functions (actor, destroy) was over-complicating things and
leading to the noted PR and also difficulties in setting
breakpoints on these functions (so this will help PR99215 as
well). The revised mangling matches the form used by
Hi,
This is primarily a source code refactoring, the only change is to
ensure that the outlined functions are marked to begin at the same
line as the original. Otherwise, they get the default (which seems
to be input_location, which corresponds to the closing brace at the
point that this is
Hi,
When amending the function re-write code, I made a typo in
the block connections. This has not shown up in any test
fails (as far as can be seen) but is a regression in debug
info.
Fixed thus.
tested on x86_64-darwin, linux,
pushed to master as obvious, I plan to back-port it where needed
Hi,
There were two uses for the Darwin host config fragment:
The first is to arrange for targets that support mdynamic-no-pic
to be built with that enabled (since it makes a significant
difference to the compiler performance). We can be more specific
in the application of this, since it only
On 7/9/21 2:16 AM, Maxim Kuvyrkov via Gcc-patches wrote:
On 9 Jul 2021, at 02:35, sunil.k.pandey via Gcc-patches
wrote:
On Linux/x86_64,
a110855667782dac7b674d3e328b253b3b3c919b is the first bad commit
commit a110855667782dac7b674d3e328b253b3b3c919b
Author: Martin Sebor
Date: Wed Jul 7
On Fri, Jul 09, 2021 at 08:43:59AM +0200, Richard Biener wrote:
> I wonder if there's a way to query the target what modes the doloop
> pattern can handle (not being too familiar with the doloop code).
You can look what modes are allowed for operand 0 of doloop_end,
perhaps? Although that is a
On 7/9/21 12:16 AM, Richard Biener wrote:
On Thu, Jul 8, 2021 at 8:02 PM Martin Sebor via Gcc-patches
wrote:
Hi Ian,
Yesterday's enhancement to -Warray-bounds has exposed a couple of
issues in libgo where the code writes into an invalid constant
address that the warning is designed to flag.
> Tested on x86-64/Linux, applied on the mainline, 11 and 10 branches.
>
>
> 2021-05-21 Eric Botcazou
>
> * gcc-interface/decl.c (gnat_to_gnu_subprog_type): Always translate
> the Is_Pure flag into the "pure" attribute of GNU C.
This is the missing piece, applied on the same
On Mon, Jul 5, 2021 at 6:00 PM H.J. Lu wrote:
>
> Since for gnux32 hosts, -m32 generates i386 codes, always check __x86_64__
> for x86 hosts.
>
> PR libffi/101336
> * configure.host: Always check __x86_64__ for x86 hosts.
> ---
> libffi/configure.host | 21 +++--
>
Hi,
On Thu, Jul 08 2021, Qing Zhao wrote:
> (Resend this email since the previous one didn’t quote, I changed one
> setting in my mail client, hopefully that can fix this issue).
>
> Hi, Martin,
>
> Thank you for the review and comment.
>
>> On Jul 8, 2021, at 8:29 AM, Martin Jambor wrote:
>>>
Hi Paul,
On 6/8/21 2:11 PM, Paul A. Clarke via Gcc-patches wrote:
Copy the test for _mm_minpos_epu16 from
gcc/testsuite/gcc.target/i386/sse4_1-phminposuw.c, with
a few adjustments:
- Adjust the dejagnu directives for powerpc platform.
- Make the data not be monotonically increasing,
such
Hi Paul,
On 6/8/21 2:11 PM, Paul A. Clarke via Gcc-patches wrote:
Add a naive implementation of the subject x86 intrinsic to
ease porting.
"subject" won't be part of eventual commit, so please specify in commit
blurb.
2021-06-08 Paul A. Clarke
gcc/ChangeLog:
*
On Thu, Jul 08, 2021 at 08:26:45PM -0500, Peter Bergner wrote:
> On 7/8/21 6:28 PM, Segher Boessenkool wrote:
> >> int index = WORDS_BIG_ENDIAN ? i : nvecs - 1 - i;
> >> -rtx dst_i = gen_rtx_REG (reg_mode, reg + index);
> >> -emit_insn (gen_rtx_SET (dst_i, XVECEXP (src, 0,
2021-07-09 Uroš Bizjak
gcc/
* recog.c (memory_address_addr_space_p): Change the type to bool.
Return true/false instead of 1/0.
(offsettable_memref_p): Ditto.
(offsettable_nonstrict_memref_p): Ditto.
(offsettable_address_addr_space_p): Ditto.
Change the type of addressp
Generate the marker for -fno-direct-extern-access to indicate that the
object file uses GOT to access all external symbols. Access to protected
symbols in the resulting shared library is treated as local, which requires
canonical function pointers and cannot be used with copy relocation.
Changes in the v2 patch.
1. GNU_PROPERTY_1_NEEDED_INDIRECT_EXTERN_ACCESS support has been added to
GNU binutils 2.38. But the -z indirect-extern-access linker option is
only available for Linux/x86. However, the --max-cache-size=SIZE linker
option was also addded within a day.
-fdirect-extern-access is the default. With -fno-direct-extern-access:
1. Always use GOT to access undefined data and function symbols,
including in PIE and non-PIE. These will avoid copy relocations
in executables. This is compatible with existing executables and
shared libraries.
2.
On Thu, 8 Jul 2021, Jason Merrill wrote:
> On 7/8/21 11:28 AM, Patrick Palka wrote:
> > Here we're crashing ultimately because the mechanism for delaying
> > substitution into a requires-expression (or constexpr if) doesn't
> > expect to see dependent args. But we end up capturing dependent
> >
Hi Martin,
>> Yesterday's enhancement to -Warray-bounds has exposed a couple of
>> issues in libgo where the code writes into an invalid constant
>> address that the warning is designed to flag.
>>
>> On the assumption that those invalid addresses are deliberate,
>> the attached patch suppresses
> On 9 Jul 2021, at 09:16, Richard Biener via Gcc-patches
> wrote:
>
> On Thu, Jul 8, 2021 at 8:02 PM Martin Sebor via Gcc-patches
> wrote:
>>
>> Hi Ian,
>>
>> Yesterday's enhancement to -Warray-bounds has exposed a couple of
>> issues in libgo where the code writes into an invalid constant
Thanks for the review.
Richard Biener writes:
>> @@ -588,6 +600,23 @@ public:
>>/* Unrolling factor */
>>poly_uint64 vectorization_factor;
>>
>> + /* If this loop is an epilogue loop whose main loop can be skipped,
>> + MAIN_LOOP_EDGE is the edge from the main loop to this loop's
Style cleanup only.
Tested on x86_64-pc-linux-gnu, committed on trunk
gcc/ada/
* exp_put_image.adb (Make_Put_Image_Name): Fix style.
(Image_Should_Call_Put_Image): Likewise.
(Build_Image_Call): Likewise.diff --git a/gcc/ada/exp_put_image.adb b/gcc/ada/exp_put_image.adb
Before this commit, the following piece of code:
procedure Main is
function F (X : access Integer) return Boolean with Import;
begin
null;
end;
Resulted in the following error messages:
main.adb:2:59: error: ";" should be "is"
main.adb:5:01: error: "end F;" expected
main.adb:5:01: error:
In Ada 2022 mode, the compiler crashes when generating the Put_Image
function for a tagged type if the parent subtype is constrained.
Tested on x86_64-pc-linux-gnu, committed on trunk
gcc/ada/
* exp_put_image.adb (Make_Component_Attributes): Use
Implementation_Base_Type to get
Add IPV6_FLOWINFO and IF_NAMESIZE values into generated package
System.OS_Constants.
Tested on x86_64-pc-linux-gnu, committed on trunk
gcc/ada/
* gsocket.h: Include net/if.h to get IF_NAMESIZE constant.
* s-oscons-tmplt.c: Define IPV6_FLOWINFO for Linux.diff --git
The previous implementation could exhibit quadratic behavior in some
cases (e.g., if the input was already sorted or almost sorted). The
new implementation uses an N log N worst case algorithm.
Tested on x86_64-pc-linux-gnu, committed on trunk
gcc/ada/
* libgnat/a-cdlili.adb:
This patch fixes an issue in the compiler whereby an assignment to a
limited interface access type causes a crash when the right hand side
has an unresolvable function call in prefix notation and verbose errors
are enabled via (-gnatf).
Tested on x86_64-pc-linux-gnu, committed on trunk
gcc/ada/
Improve existing support for the Ada extension feature of casing on
composite values to handle casing on values that are discriminated or
have discriminated subcomponents.
Tested on x86_64-pc-linux-gnu, committed on trunk
gcc/ada/
* exp_ch5.adb (Expand_General_Case_Statement): Add new
This patch fixes an issue in the compiler whereby a pragma Inline
appearing after a subprogram body stub to which it applies and where no
specification is present causes a compile time crash.
Tested on x86_64-pc-linux-gnu, committed on trunk
gcc/ada/
* sem_ch6.adb (Check_Pragma_Inline):
The declaration of time_t is in flux based on it's overflow in Year
2038, so declare it uniformly based on System.Parameter.time_t_bits
to ease this transition and also enable VxWorks targets which allow
it to be parameterized, to be rebuilt more easily by one source change.
Two changes of note:
...in case Current_Error_Node is Empty, which will cause it to print "No
source file position information available". At least now we have the
file name being compiled.
Tested on x86_64-pc-linux-gnu, committed on trunk
gcc/ada/
* comperr.adb (Compiler_Abort): Print source file
Fix layout of contracts in libgnat/a-strunb.ads and
libgnat/a-strunb__shared.ads so that it is the same in both files.
Tested on x86_64-pc-linux-gnu, committed on trunk
gcc/ada/
* libgnat/a-strunb.ads, libgnat/a-strunb__shared.ads: Fix layout
in contracts.diff --git
This prevents the output of -gnatRj from containing several "variant" fields
for an extension with a variant part of a tagged type with a variant part.
Tested on x86_64-pc-linux-gnu, committed on trunk
gcc/ada/
* repinfo.ads (JSON output format): Document adjusted key name.
*
Minor typo; found while fixing handling of tagged types in GNATprove.
Tested on x86_64-pc-linux-gnu, committed on trunk
gcc/ada/
* exp_util.ads (Map_Types): Fix typo.diff --git a/gcc/ada/exp_util.ads b/gcc/ada/exp_util.ads
--- a/gcc/ada/exp_util.ads
+++ b/gcc/ada/exp_util.ads
@@ -915,7
This in particular documents the new warning given on overlays.
Tested on x86_64-pc-linux-gnu, committed on trunk
gcc/ada/
* doc/gnat_rm/implementation_defined_attributes.rst
(Scalar_Storage_Order): Add paragraph about representation
changes.
* gnat_rm.texi:
Since newlib doesn't implement correctly long double, use the wraplf
variant for a-nallfl.
Tested on x86_64-pc-linux-gnu, committed on trunk
gcc/ada/
* Makefile.rtl (LIBGNAT_TARGET_PAIRS) : Use
the wraplf variant of Aux_Long_Long_Float.diff --git a/gcc/ada/Makefile.rtl
Explicitly initialize local variables related to analysis of expression
functions to prevent spurious checks from static analysers.
Tested on x86_64-pc-linux-gnu, committed on trunk
gcc/ada/
* sem_ch6.adb (Analyze_Expression_Function): Initialize Orig_N
and Typ variables.diff
We need to declare a predicate function along with its type but can only
generate the body at freeze point which may be in a separate scope,
leading to inconsistencies. So fix this by deferring the generation of
the predicate function declaration and fix latent bugs uncovered along
the way.
While
This patch corrects various issues discovered during testing of the
No_Dynamic_Accessibility_Checks restriction leading to level
miscalculation errors.
Tested on x86_64-pc-linux-gnu, committed on trunk
gcc/ada/
* sem_util.ads (Type_Access_Level): Add new optional parameter
This updates the documentation of the debugging information generated by
the compiler present in the spec of the Exp_Dbug unit.
Tested on x86_64-pc-linux-gnu, committed on trunk
gcc/ada/
* exp_dbug.ads: Update documentation of various items.diff --git a/gcc/ada/exp_dbug.ads
Group two variants of preanalysis of expression functions. Code cleanup
related to handling of static expression functions in GNATprove.
Tested on x86_64-pc-linux-gnu, committed on trunk
gcc/ada/
* sem_ch6.adb (Analyze_Expression_Function): Reorder code.diff --git a/gcc/ada/sem_ch6.adb
Analysis of static expression functions happened inside an IF branch
guarded by GNATprove_Mode. Cleanup related to handling of static
expression functions in GNATprove mode; behaviour is unaffected.
Tested on x86_64-pc-linux-gnu, committed on trunk
gcc/ada/
* sem_ch6.adb
Cleanup related to handing of static expression functions in GNATprove.
Tested on x86_64-pc-linux-gnu, committed on trunk
gcc/ada/
* sem_ch6.adb (Analyze_Expression_Function): Add variable to
avoid repeated calls to Etype.diff --git a/gcc/ada/sem_ch6.adb b/gcc/ada/sem_ch6.adb
Cleanup related to handing of static expression functions in GNATprove.
Tested on x86_64-pc-linux-gnu, committed on trunk
gcc/ada/
* sem_ch6.adb (Analyze_Expression_Function): Fix comment.diff --git a/gcc/ada/sem_ch6.adb b/gcc/ada/sem_ch6.adb
--- a/gcc/ada/sem_ch6.adb
+++
Code cleanup related to handing of static expression functions in
GNATprove; behaviour is unaffected.
Tested on x86_64-pc-linux-gnu, committed on trunk
gcc/ada/
* sem_ch6.adb (Analyze_Expression_Function): Use Orig_N variable
instead of repeated calls to Original_Node.diff --git
Code cleanup related to handing of static expression functions in
GNATprove; behaviour is unaffected.
Tested on x86_64-pc-linux-gnu, committed on trunk
gcc/ada/
* sem_ch6.adb (Analyze_Expression_Function): Change types local
variables from Entity_Id to Node_Id.diff --git
Code cleanup related to preanalysis in GNATprove mode; behaviour is
unaffected.
Tested on x86_64-pc-linux-gnu, committed on trunk
gcc/ada/
* sem_ch6.adb (Analyze_Expression_Function): A local Expr
constant was shadowing a global constant with the same name and
the same
Cleanup related to preanalysis in GNATprove mode; behaviour is
unaffected.
Tested on x86_64-pc-linux-gnu, committed on trunk
gcc/ada/
* sem_res.adb (Preanalyze_And_Resolve): Only call
Set_Must_Not_Freeze when it is necessary to restore the previous
value.diff --git
On Fri, Jul 9, 2021 at 1:54 PM Richard Sandiford via Gcc-patches
wrote:
>
> Kyrylo Tkachov writes:
> >> -Original Message-
> >> From: Richard Sandiford
> >> Sent: 09 July 2021 12:40
> >> To: Jonathan Wright
> >> Cc: gcc-patches@gcc.gnu.org; Kyrylo Tkachov
> >> Subject: Re: [PATCH]
On Thu, Jul 8, 2021 at 2:50 PM Richard Sandiford via Gcc-patches
wrote:
>
> This patch adds support for reusing a main loop's reduction accumulator
> in an epilogue loop. This in turn lets the loops share a single piece
> of vector->scalar reduction code.
>
> The patch has the following
Kyrylo Tkachov writes:
>> -Original Message-
>> From: Richard Sandiford
>> Sent: 09 July 2021 12:40
>> To: Jonathan Wright
>> Cc: gcc-patches@gcc.gnu.org; Kyrylo Tkachov
>> Subject: Re: [PATCH] aarch64: Use unions for vector tables in vqtbl[234]
>> intrinsics
>>
>> Jonathan Wright
> -Original Message-
> From: Richard Sandiford
> Sent: 09 July 2021 12:40
> To: Jonathan Wright
> Cc: gcc-patches@gcc.gnu.org; Kyrylo Tkachov
> Subject: Re: [PATCH] aarch64: Use unions for vector tables in vqtbl[234]
> intrinsics
>
> Jonathan Wright writes:
> > Hi,
> >
> > As
Jonathan Wright writes:
> Hi,
>
> As subject, this patch uses a union instead of constructing a new opaque
> vector structure for each of the vqtbl[234] Neon intrinsics in arm_neon.h.
> This simplifies the header file and also improves code generation -
> superfluous move instructions were
On Thu, Jul 8, 2021 at 6:48 PM Richard Sandiford
wrote:
>
> Richard Biener writes:
> > On Thu, Jul 8, 2021 at 2:46 PM Richard Sandiford via Gcc-patches
> > wrote:
> >>
> >> This patch passes the reduc_info to get_initial_defs_for_reduction,
> >> so that the function can get general information
Hello
This is a WIP implementation of metadirectives as defined in the OpenMP 5.0
spec. I intend to add support for metadirectives as specified in OpenMP 5.1
later (where the directive can be selected dynamically at runtime), but am
concentrating on the static part for now. Parsing has only
Xi Ruoyao writes:
> On Thu, 2021-07-08 at 17:44 -0600, Jeff Law wrote:
>>
>>
>> On 6/25/2021 8:40 AM, Richard Sandiford wrote:
>> > Xi Ruoyao via Gcc-patches writes:
>> > > On Fri, 2021-06-25 at 01:02 +0800, Xi Ruoyao wrote:
>> > > > On Thu, 2021-06-24 at 10:48 -0600, Jeff Law wrote:
>> > > >
Hi,
As subject, this patch uses a union instead of constructing a new opaque
vector structure for each of the vqtbl[234] Neon intrinsics in arm_neon.h.
This simplifies the header file and also improves code generation -
superfluous move instructions were emitted for every register
extraction/set
On Fri, Jul 9, 2021 at 9:16 AM Andrew Pinski wrote:
>
> On Thu, Jul 8, 2021 at 11:50 PM Richard Biener via Gcc-patches
> wrote:
> >
> > On Fri, Jul 9, 2021 at 7:34 AM apinski--- via Gcc-patches
> > wrote:
> > >
> > > From: Andrew Pinski
> > >
> > > Instead of waiting for DCE to remove the
In addition to the obvious cut-n-pasto where *udivmodsi4_pow2_zext_2
never matches, limit the range of the immediate operand to prevent
out of range immediate operand of AND instruction.
Found by inspection, the patterns rarely match (if at all), since
tree optimizers do the transformation before
On Fri, Jul 9, 2021 at 9:41 AM Eric Botcazou wrote:
>
> Hi,
>
> this is the build failure on Windows with binutils for which GNU as accepts
> the --gdwarf-5 switch but GNU ld generates broken binaries with DWARF 5.
>
> We already have the HAVE_LD_BROKEN_PE_DWARF5 kludge to disable DWARF 5 in this
The driver amends assembler options with for example --gdwarf-5
when debugging is enabled but the check for that does not consider
the effect of -gtoggle which is not handled in the common option
machinery. The following alters debug_info_level according to
-gtoggle mimicing what process_options
> On 9 Jul 2021, at 09:57, Uros Bizjak wrote:
>
> On Fri, Jul 9, 2021 at 10:25 AM Iain Sandoe wrote:
>>
>> (early) ping;
>> if possible I’d like to get this onto master in time to back-port for 11.2.
>>
>>> On 4 Jul 2021, at 21:08, Iain Sandoe wrote:
>>>
>>> Hi,
>>>
>>> (I’m not going
On Fri, Jul 9, 2021 at 10:25 AM Iain Sandoe wrote:
>
> (early) ping;
> if possible I’d like to get this onto master in time to back-port for 11.2.
>
> > On 4 Jul 2021, at 21:08, Iain Sandoe wrote:
> >
> > Hi,
> >
> > (I’m not going to defend the status quo here, it seems a bit prone
> > to
(early) ping;
if possible I’d like to get this onto master in time to back-port for 11.2.
> On 4 Jul 2021, at 21:08, Iain Sandoe wrote:
>
> Hi,
>
> (I’m not going to defend the status quo here, it seems a bit prone
> to confusing a user [different interposition behaviour between the
> inlined
> On 9 Jul 2021, at 02:35, sunil.k.pandey via Gcc-patches
> wrote:
>
> On Linux/x86_64,
>
> a110855667782dac7b674d3e328b253b3b3c919b is the first bad commit
> commit a110855667782dac7b674d3e328b253b3b3c919b
> Author: Martin Sebor
> Date: Wed Jul 7 14:05:25 2021 -0600
>
>Correct
Hi,
this is the build failure on Windows with binutils for which GNU as accepts
the --gdwarf-5 switch but GNU ld generates broken binaries with DWARF 5.
We already have the HAVE_LD_BROKEN_PE_DWARF5 kludge to disable DWARF 5 in this
case but it only tames the DWARF version in the compiler, so
On Thu, Jul 8, 2021 at 11:50 PM Richard Biener via Gcc-patches
wrote:
>
> On Fri, Jul 9, 2021 at 7:34 AM apinski--- via Gcc-patches
> wrote:
> >
> > From: Andrew Pinski
> >
> > Instead of waiting for DCE to remove the unused statement,
> > and maybe optimize another conditional, it is better if
On Thu, Jul 8, 2021 at 7:56 AM Segher Boessenkool
wrote:
>
> On Wed, Jul 07, 2021 at 11:32:59PM +0800, Hongtao Liu wrote:
> > On Wed, Jul 7, 2021 at 10:54 PM Segher Boessenkool
> > wrote:
> > > So, a "FAKE_CALL" is very much a *real* call, on the RTL level, which is
> > > where we are here. But
On Fri, Jul 9, 2021 at 7:35 AM apinski--- via Gcc-patches
wrote:
>
> From: Andrew Pinski
>
> Previously the idea was gimple_simplify_phiopt would call
> resimplify with a NULL sequence but that sometimes fails
> even if there was only one statement produced. The cases
> where it fails is when
Ping again.
On Mon, 2021-06-28 at 21:50 +0800, Xi Ruoyao wrote:
> Ping. CC several maintainers who may help to review MIPS patches.
> Sorry if it sounds buzzing.
>
> On Wed, 2021-06-23 at 11:11 +0800, Xi Ruoyao wrote:
> > Commit message shamelessly copied from 1777beb6b129 by jakub:
> >
> >
PING again.
On Thu, 2021-07-01 at 16:11 +0800, Xi Ruoyao wrote:
> Ping.
>
> On Mon, 2021-06-21 at 21:42 +0800, Xi Ruoyao wrote:
> > Middle-end started to emit vec_cmp and vec_cmpu since GCC 11,
> > causing
> > ICE on MIPS with MSA enabled. Add the pattern to prevent it.
> >
> > Bootstrapped
On Fri, Jul 9, 2021 at 7:34 AM apinski--- via Gcc-patches
wrote:
>
> From: Andrew Pinski
>
> Instead of waiting for DCE to remove the unused statement,
> and maybe optimize another conditional, it is better if
> we don't move the statement and have the statement
> removed.
>
> gcc/ChangeLog:
>
>
On Fri, 2021-07-09 at 14:01 +0800, Xi Ruoyao wrote:
> On Thu, 2021-07-08 at 17:20 -0600, Jeff Law wrote:
> >
> > On 7/5/2021 8:04 PM, Paul Hua wrote:
> > > Looks good to me, but I have no right to approve.
> > But your opinions are well respected :-)
> >
> > I'll go ahead and ACK, though in
On Fri, Jul 9, 2021 at 4:39 AM Jeff Law wrote:
>
>
>
> On 7/2/2021 10:13 AM, Jeff Law wrote:
> >
> > This is a minor missed optimization we found with our internal port.
> >
> > Given this code:
> >
> > typedef struct {short a; short b;} T;
> >
> > extern void g1();
> >
> > void f(T s)
> > {
> >
On Fri, 9 Jul 2021, Jiufu Guo wrote:
> Currently, doloop.xx variable is using the type as niter which may shorter
> than word size. For some cases, it may be better to use word size type.
> For example, on some 64bit system, to access 32bit niter, subreg maybe used.
> Then using 64bit type would
On Thu, 2021-07-08 at 17:44 -0600, Jeff Law wrote:
>
>
> On 6/25/2021 8:40 AM, Richard Sandiford wrote:
> > Xi Ruoyao via Gcc-patches writes:
> > > On Fri, 2021-06-25 at 01:02 +0800, Xi Ruoyao wrote:
> > > > On Thu, 2021-06-24 at 10:48 -0600, Jeff Law wrote:
> > > > > I'd like to know a bit
On Fri, Jul 9, 2021 at 12:57 AM Martin Sebor via Gcc-patches
wrote:
>
> To unblock bootstrap this morning that was failing due to stricter
> array bounds checking, I suppressed two -Warray-bounds instances
> in cp/modules.cc without analyzing them, tracking the to-do in
> pr101372. Now that I
On Thu, Jul 8, 2021 at 8:02 PM Martin Sebor via Gcc-patches
wrote:
>
> Hi Ian,
>
> Yesterday's enhancement to -Warray-bounds has exposed a couple of
> issues in libgo where the code writes into an invalid constant
> address that the warning is designed to flag.
>
> On the assumption that those
1 - 100 of 101 matches
Mail list logo
