On Mon, 2022-07-04 at 21:21 -0700, Fangrui Song wrote:
> Clang considers that asan/msan/tsan/dataflow/etc enables
> -fasynchronous-unwind-tables by default so I assume this GCC change is
> fine.
I agree it's fine, but the problem is TSAN is currently "unsupported"
within GCC (i. e. when you build
On Mon, Jul 4, 2022 at 6:54 PM Xi Ruoyao via Gcc-patches
wrote:
>
> On Mon, 2022-07-04 at 14:28 +, Dimitrije Milosevic wrote:
> > On Saturday, June 11, 2022 2:03 PM, Xi wrote:
> > > Just tried TSAN_SUPPORTED=yes with asynchronous unwind tables
> > > enabled,
> > > but I got some strange test
> -Original Message-
> From: Martin Liška
> Sent: Monday, July 4, 2022 6:17 PM
> To: gcc-patches@gcc.gnu.org
> Cc: Jiang, Haochen
> Subject: [PATCH][pushed] MAINTAINERS: fix alphabetic sorting
>
> ChangeLog:
>
> * MAINTAINERS: fix sorting of names
> ---
> MAINTAINERS | 2 +-
> 1
On Mon, 2022-07-04 at 14:28 +, Dimitrije Milosevic wrote:
> On Saturday, June 11, 2022 2:03 PM, Xi wrote:
> > Just tried TSAN_SUPPORTED=yes with asynchronous unwind tables
> > enabled,
> > but I got some strange test failures for tls_race.c:
> >
> > FAIL: c-c++-common/tsan/tls_race.c -O0
On Mon, 27 Jun 2022, Xi Ruoyao via Gcc-patches wrote:
> egrep has been deprecated in favor of grep -E for a long time, and the
> next GNU grep release (3.8 or 4.0) will print a warning if egrep is used.
> Unfortunately, old hosts with non-GNU grep may lack the support for -E
> option. Use
On Tue, Jul 5, 2022 at 1:48 AM Roger Sayle wrote:
>
>
> Hi Hongtao,
> Many thanks for your review. This revised patch implements your
> suggestions of removing the combine splitters, and instead reusing
> the functionality of the ssse3_palignrdi define_insn_and split.
>
> This revised patch has
See gcc/config/newlib-stdint.h, where targets that have
LONG_TYPE_SIZE == 32, get INT32_TYPE defined to "long int".
INT32_TYPE ends up in the target int32_t.
Thus the tests failed for 32-bit newlib targets due to related
warning messages being matched to "aka int" where the emitted
message for
On Linux/x86_64,
b110e5283e368b5377e04766e4ff82cd52634208 is the first bad commit
commit b110e5283e368b5377e04766e4ff82cd52634208
Author: Martin Jambor
Date: Fri Jul 1 20:57:18 2022 +0200
tree-sra: Fix union handling in build_reconstructed_reference
caused
FAIL:
*This patch is the initial implementation of OpenMP-API specs book section
**20.5.5 with title "Thread Handles".*
*I have fixed the first version after revising the notes on it.*
*libgomp/ChangeLog
2022-07-01 Ahmed Sayed >
*
** Makefile.am (libgompd_la_SOURCES): Add ompd-threads.c.*
**
This patch is the latest revision of the patch originally posted at:
https://gcc.gnu.org/pipermail/gcc-patches/2022-June/596201.html
This patch extends the earlier and;cmp to not;test optimization to also
perform this transformation for TImode on TARGET_64BIT and DImode on -m32,
One motivation
On Linux/x86_64,
d2a89809452ef79a14feae1cadc3538e4b45 is the first bad commit
commit d2a89809452ef79a14feae1cadc3538e4b45
Author: Richard Biener
Date: Tue Jun 21 16:17:58 2022 +0200
Put virtual operands into loop-closed SSA
caused
FAIL: 25_algorithms/find_end/constrained.cc
On Mon, Jul 04, 2022 at 08:29:37PM +0200, Tobias Burnus wrote:
> Fortran part to C/C++
> commit r13-1002-g03b71406323ddc065b1d7837d8b43b17e4b048b5
>
> gcc/fortran/ChangeLog:
>
> * gfortran.h (gfc_omp_namelist): Update by creating 'linear' struct,
> move 'linear_op' as 'op' to id and
On Mon, Jul 4, 2022 at 7:27 PM Roger Sayle wrote:
>
>
> Hi Uros,
> Thanks for the review. This patch implements all of your suggestions, both
> removing ix86_pre_reload_split from the combine splitter(s), and dividing
> the original splitter up into four simpler variants, that use match_dup to
>
The following converts a handful of places that were irange centric.
Tested on x86-64 Linux.
gcc/ChangeLog:
* gimple-range-fold.cc
(fold_using_range::range_of_ssa_name_with_loop_info): Restrict the
call to SCEV for irange supported types.
Ping!!
> -Original Message-
> From: Gcc-patches bounces+srinath.parvathaneni=arm@gcc.gnu.org> On Behalf Of Srinath
> Parvathaneni via Gcc-patches
> Sent: 05 May 2022 12:02
> To: gcc-patches@gcc.gnu.org
> Cc: Richard Earnshaw
> Subject: [PATCH v2][GCC] arm: Add support for dwarf
On 04.07.22 19:20, Jakub Jelinek wrote:
Perhaps you could avoid some code duplication by doing it like:
bool close_paren = gfc_match ("val )") == MATCH_YES;
if (close_paren || gfc_match ("val , ") == MATCH_YES)
Done!
Good idea! I was thinking of things
Hi Hongtao,
Many thanks for your review. This revised patch implements your
suggestions of removing the combine splitters, and instead reusing
the functionality of the ssse3_palignrdi define_insn_and split.
This revised patch has been tested on x86_64-pc-linux-gnu with make
bootstrap and make
Hi Uros,
Thanks for the review. This patch implements all of your suggestions, both
removing ix86_pre_reload_split from the combine splitter(s), and dividing
the original splitter up into four simpler variants, that use match_dup to
handle the variants/permutations caused by operator
Applied slight tweak to the patch for the gcc12 branch.
botstrapped and no regressions on x86_64-pc-linux-gnu. Pushed.
Andrew
Forwarded Message
Subject: [COMMITTED] PR tree-optimization/106114 - Don't use gori
dependencies to optimize.
Date: Wed, 29 Jun 2022 21:40:44
On Mon, Jul 04, 2022 at 06:09:31PM +0200, Tobias Burnus wrote:
> thanks for the comment & spec referral. I have now updated the patch –
> and included the new C/Fortran testcase.
Thanks.
> + while (true)
> + {
> + old_loc = gfc_current_locus;
> +
On 5/16/2022 5:27 AM, Tomas Kalibera via Gcc-patches wrote:
On 5/11/22 18:43, Joseph Myers wrote:
There are various coding style issues in the patch; at least missing
space
before '(' and '&&' at end of line (should be at start of line). It
will
also need to be updated for .c files having
On Thu, 30 Jun 2022 at 16:15, Marek Polacek wrote:
>
> On Thu, Jun 30, 2022 at 04:11:42PM +0100, Jonathan Wakely via Gcc-patches
> wrote:
> > I recently changed to no longer include an unnecessary header,
> > which meant it no longer includes , which means it no longer
> > includes . This
Hi Jakub,
thanks for the comment & spec referral. I have now updated the patch –
and included the new C/Fortran testcase.
On 04.07.22 16:53, Jakub Jelinek via Fortran wrote:
See OpenMP 5.2 [59:31-34]:
A modifier that is an expression must neither lexically match the name of a
simple modifier
On Mon, Jun 27, 2022 at 06:31:18PM +0200, Jakub Jelinek via Gcc-patches wrote:
> Because the late evaluation of the initializer could have touched
> the destination, so we need to reevaluate it.
> Same reason why we call get_or_insert_ctor_field again in the second
> loop as we call it in the
On Thu, Jun 30, 2022 at 01:40:24PM +0200, Jakub Jelinek via Gcc-patches wrote:
> On Fri, Jun 10, 2022 at 03:59:37PM +0200, Marcel Vollweiler wrote:
> > > I'm not sure we can rely on execv on all targets that do support libgomp.
> > > Any reason why you actually need this, rather than using
> > >
On Mon, Jul 04, 2022 at 04:10:03PM +0200, Tobias Burnus wrote:
> This patch adds support for the OpenMP 5.2 syntax for the linear clause,
> following the C/C++ patch. The testcases are modified versions from the
> C/C++ ones, plus one added one for duplicated modifiers.
>
> At least to me it is
Hi,
On Mon, Jul 04 2022, Richard Biener wrote:
> On Fri, 1 Jul 2022, Martin Jambor wrote:
>
>> Hi,
>>
>> As the testcase in PR 105860 shows, the code that tries to re-use the
>> handled_component chains in SRA can be horribly confused by unions,
>> where it thinks it has found a compatible
Richard Earnshaw writes:
> On 01/07/2022 14:03, Richard Earnshaw via Gcc-patches wrote:
>> On 28/04/2022 10:40, Andrea Corallo via Gcc-patches wrote:
>>> Add targeting-checking entities for PACBTI in testsuite
>>> framework.
>>>
>>> Pre-approved with the requested changes here
>>>
On Saturday, June 11, 2022 2:03 PM, Xi wrote:
> Just tried TSAN_SUPPORTED=yes with asynchronous unwind tables enabled,
> but I got some strange test failures for tls_race.c:
>
> FAIL: c-c++-common/tsan/tls_race.c -O0 output pattern test
> Output was:
> ThreadSanitizer: CHECK failed:
On 7/1/22 08:36, Richard Biener wrote:
> On Thu, Jun 30, 2022 at 10:42 AM Martin Liška wrote:
>>
>> On 6/30/22 08:43, Rui Ueyama wrote:
>>> Thanks Martin for creating this patch.
>>
>> You're welcome.
>>
>>>
>>> Here is a preliminary change for the mold side:
>>>
We have unordered FP comparisons implemented as RTL insns that produce
multiple machine instructions. Such RTL insns are hard to match with a
processor pipeline description and additionally there is a redundant
SNEZ instruction produced on the result of these comparisons even though
the
This patch adds support for the OpenMP 5.2 syntax for the linear clause,
following the C/C++ patch. The testcases are modified versions from the
C/C++ ones, plus one added one for duplicated modifiers.
At least to me it is not quite clear when
linear ( var : ref)
refers to a variable 'ref' and
The testcase shows that when cleaning up the CFG we can end up
with broken LC SSA (for virtual operands with the testcase). The
case here involves deleting a loop after which it is not enough
to scan the blocks with changed loop depth for SSA uses that need
to be rewritten. So make
On 7/4/22 14:28, Richard Biener wrote:
> ... but ... is libatomic properly built for the host? libgo is a
> target library.
You're correct.
Well, so the host library should be taken, which works for stage1 lto-plugin:
[ 668s] libtool: link: gcc -shared -fPIC -DPIC .libs/lto-plugin.o
The final loop IV use after the loop has that not in LC SSA
(and inserts not simplified _2 = _3 - 0 stmts). In particular
since it splits the exit edge when there's a virtual PHI in the
destination it breaks virtual LC SSA form (but likely also
non-virtual).
The following properly inserts LC
The following reverts the just added assert that virtual SSA does not
need updating. It instead goes for a select whitelist of transforms
known to be prone to difficulties with virtual SSA update.
Bootstrapped and tested on x86_64-unknown-linux-gnu, tested on
aarch64 on the vect.exp testsuite
On Mon, Jul 4, 2022 at 2:28 PM Richard Biener
wrote:
>
> On Mon, Jul 4, 2022 at 1:32 PM Martin Liška wrote:
> >
> > Similarly to libgo, we need to provide -L for targets where
> > libpthread does depends on libatomic.
> >
> > Ready for master?
>
> OK
... but ... is libatomic properly built for
On Mon, Jul 4, 2022 at 1:32 PM Martin Liška wrote:
>
> Similarly to libgo, we need to provide -L for targets where
> libpthread does depends on libatomic.
>
> Ready for master?
OK
> PR bootstrap/106156
>
> lto-plugin/ChangeLog:
>
> * Makefile.am: Use PTHREAD_CFLAGS.
> *
Similarly to libgo, we need to provide -L for targets where
libpthread does depends on libatomic.
Ready for master?
PR bootstrap/106156
lto-plugin/ChangeLog:
* Makefile.am: Use PTHREAD_CFLAGS.
* Makefile.in: Regenerate.
* configure.ac: Detect if PTHREAD_CFLAGS
Xi Ruoyao via Gcc-patches writes:
> On Fri, 2022-07-01 at 12:40 +, Dimitrije Milosevic wrote:
>> Building the ASAN for the n32 MIPS ABI currently fails, due to a few reasons:
>> - defined(__mips64), which is set solely based on the architecture type
>> (32-bit/64-bit),
>> was still used in
On Mon, 4 Jul 2022, Richard Biener wrote:
> The following removes a FIXME where we fail(ed) to keep virtual
> SSA up-to-date, patching up the remaining two cases I managed to
> trigger. I've left an assert so that we pick up cases arising
> for the cases I wasn't able to trigger.
>
>
On 04/07/2022 10:27, Andrea Corallo via Gcc-patches wrote:
Richard Earnshaw writes:
[...]
+@item
+-mbranch-protection=@var{none}|@var{standard}|@var{pac-ret}[+@var{leaf}][+@var{bti}]|@var{bti}[+@var{pac-ret}[+@var{leaf}]]
+@opindex mbranch-protection
+Enable branch protection features
The following removes a FIXME where we fail(ed) to keep virtual
SSA up-to-date, patching up the remaining two cases I managed to
trigger. I've left an assert so that we pick up cases arising
for the cases I wasn't able to trigger.
Bootstrapped and tested on x86_64-unknown-linux-gnu, I've also
On Mon, Jul 04, 2022 at 12:15:00PM +0200, Martin Liška wrote:
> I've made the mistake multiple times while doing a bisection.
> One would expect that gcc-descr w/o an argument would print
> revision for the current HEAD and not master.
> Thus change it.
>
> Ready to be installed?
> Thanks,
>
ChangeLog:
* MAINTAINERS: fix sorting of names
---
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index f4a11cdc755..7d9aab76dd9 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -463,8 +463,8 @@ Andreas Jaeger
I've made the mistake multiple times while doing a bisection.
One would expect that gcc-descr w/o an argument would print
revision for the current HEAD and not master.
Thus change it.
Ready to be installed?
Thanks,
Martin
contrib/ChangeLog:
* git-descr.sh: By default print revision for
Hi Jeff,
OK.
Thanks.
And yes, I wish someone else was looking at this stuff. Rust isn't really on
my radar right now...
I have been toying with the idea of putting myself forward as a maintainer
for the libiberty sources. I just wish that I had more free time...
Cheers
Nick
The nonzero bits and integer ranges compliment each other quite well,
and it only makes sense to make the mask a first class citizen in the
irange. We do a half assed job of keeping ranges and nonzero bits
somewhat in sync in SSA_NAME_RANGE_INFO, and the goal has always
been to integrate them
Richard Earnshaw writes:
[...]
> +@item
> +-mbranch-protection=@var{none}|@var{standard}|@var{pac-ret}[+@var{leaf}][+@var{bti}]|@var{bti}[+@var{pac-ret}[+@var{leaf}]]
> +@opindex mbranch-protection
> +Enable branch protection features (armv8.1-m.main only).
> +@samp{none} generate code without
On Mon, Jul 4, 2022 at 10:42 AM Eric Botcazou wrote:
>
> > For late generated vector types this might result in inconsistencies with
> > early (user) generated types when using LTO.
>
> Is that a problem? That's no different with regular array types.
I'm not sure - almost all types the user can
> For late generated vector types this might result in inconsistencies with
> early (user) generated types when using LTO.
Is that a problem? That's no different with regular array types.
> Is there context available somehow so we can do like the is_ overloads
> on a decl and use a default
When attempting to manually update SSA form after high-level loop
transforms such as loop versioning it is helpful when the loop-closed
SSA form includes virtual operands. While we have the special
rewrite_virtuals_into_loop_closed_ssa function that doesn't
presently scale, invoking update_ssa by
On Fri, Jul 01, 2022 at 11:08:16PM +0200, Tobias Burnus wrote:
>gomp_mutex_lock (_lock);
>
> + if (omp_requires_mask && omp_requires_mask != omp_req)
I'd use if (omp_req && omp_requires_mask && omp_requires_mask != omp_req)
e.g. for the case of mixing GCC <= 12 compiled code with GCC 13,
On Mon, Jul 4, 2022 at 10:03 AM Eric Botcazou via Gcc-patches
wrote:
>
> Hi,
>
> vector types are represented as array types with DW_AT_GNU_vector attribute in
> the debug info and a range [0 .. TYPE_VECTOR_SUBPARTS - 1]. That's obviously
> skewed toward the C family of languages, therefore the
On Mon, Jul 4, 2022 at 9:12 AM Xi Ruoyao wrote:
>
> Document a behavior change in r12-8546. Ok for wwwdocs?
OK.
> ---
> htdocs/gcc-12/changes.html | 26 ++
> 1 file changed, 26 insertions(+)
>
> diff --git a/htdocs/gcc-12/changes.html b/htdocs/gcc-12/changes.html
>
This changes the expanded code generated for if-expressions of 1-dimensional
arrays to create a static temporary on the stack if a small upper bound can
be computed for the length of a subtype covering the result. Static stack
allocation is preferred over dynamic allocation for code generation
If a constrained subtype is given when a deferred constant is declared,
then the subtype given in the completion is required (at compile time)
to be subject to a statically matching constraint. This rule was not
properly enforced in some cases and constructs that should have been
rejected were
For X'Access, the designated subtype of the access type must statically
match the nominal subtype of X. This patch fixes a bug where the error
was not detected when there is an unrelated declaration of the form "Y :
T := X;", where T is an unconstrained array subtype.
Tested on
This changes the compiler to build in place almost all objects that need
finalization and are initialized with the result of a function call, thus
saving a pair of Adjust/Finalize calls for the anonymous return object.
Tested on x86_64-pc-linux-gnu, committed on trunk
gcc/ada/
*
The RM 3.9.2(19) clause says that the controlling tag value is statically
determined to be the tag of the tagged type involved. As a matter of fact,
the call would be made dispatching only as a by-product of the propagation
of the controlling tag value to the tag-indeternminate actuals, but
This patch adds the new Generic_Keys.Key function to the set children
of Ada.Containers.
Tested on x86_64-pc-linux-gnu, committed on trunk
gcc/ada/
* libgnat/a-cbhase.ads, libgnat/a-cborse.ads,
libgnat/a-cihase.ads, libgnat/a-ciorse.ads,
libgnat/a-cohase.ads,
Hi,
vector types are represented as array types with DW_AT_GNU_vector attribute in
the debug info and a range [0 .. TYPE_VECTOR_SUBPARTS - 1]. That's obviously
skewed toward the C family of languages, therefore the attached patch changes
the lower bound to the default for the language of the
Target specific runtime files must be added to a the exclude list so the
files don't automatically get copied to other runtimes.
Tested on x86_64-pc-linux-gnu, committed on trunk
gcc/ada/
* Makefile.rtl (ADA_EXCLUDE_SRCS): Add s-qnx.ads.diff --git a/gcc/ada/Makefile.rtl
The -gnatwc switch enables warnings for test condition outcomes that are
known at compile time. Such warnings are unlikely to be useful in the
case of an assertion expression (or a subexpression thereof), so do not
generate them in that case.
Tested on x86_64-pc-linux-gnu, committed on trunk
The local function Rewrite_As_Renaming can be called twice in certain
circumstances, which is both not quite safe and unnecessary, so this
replaces it with a local variable whose value is computed only once.
No functional changes.
Tested on x86_64-pc-linux-gnu, committed on trunk
gcc/ada/
When a dispatching call is made to a primitive function with a controlling
tagged result, the call is dispatching on result and thus must return the
class-wide type of the tagged type to accommodate all possible results.
This was ensured by Expand_Dispatching_Call only in the common case where
Modify the RM to take into account the new functional container.
Tested on x86_64-pc-linux-gnu, committed on trunk
gcc/ada/
* doc/gnat_rm/the_gnat_library.rst: Add the new entry.
* gnat_rm.texi: Regenerate.
patch.diff.gz
Description: application/gzip
This changes the expanded code generated for dynamic concatenations to
use a static array subtype for the temporary created on the stack if a
small upper bound can be computed for the length of the result. Static
stack allocation is preferred over dynamic allocation for code
generation purposes.
Attribute Index, which was added to Ada 2022 by AI12-0143, is resolved
just like attribute Count. However, code duplication rightly triggered a
CodePeer warning.
Tested on x86_64-pc-linux-gnu, committed on trunk
gcc/ada/
* sem_attr.adb (Resolve_Attribute): Refactor duplicated code for
When the code responsible for giving errors on ambiguous operands of
comparison and equality operators was moved from the 1st phase (analysis)
to the 2nd phase (resolution) of semantic processing, it was incorrectly
restricted to the operator case, which was valid during the 1st phase but
is not
It was only used in specific cases for controlled types but no longer
provides any significant benefit in practice.
Tested on x86_64-pc-linux-gnu, committed on trunk
gcc/ada/
* debug.adb (d.9): Remove usage.
* exp_ch6.adb (Expand_Simple_Function_Return): Remove redundant
This patch corrects an issue in the compiler whereby calling
Quote_Argument with an argument that is of size 1 may lead to a
CONSTRAINT_ERROR raised at runtime due to an undersized buffer.
Tested on x86_64-pc-linux-gnu, committed on trunk
gcc/ada/
* libgnat/s-os_lib.adb
All assertion pragmas are enabled by default when using -gnata. We need
to add the GNAT specific ones to the list.
Tested on x86_64-pc-linux-gnu, committed on trunk
gcc/ada/
* doc/gnat_ugn/building_executable_programs_with_gnat.rst
(Debugging and Assertion Control): Add GNAT
Add predicates on subtypes E and N.
Tested on x86_64-pc-linux-gnu, committed on trunk
gcc/ada/
* einfo-utils.ads, einfo-utils.adb: Add predicates on subtypes E
and N. Change some parameters to use the unpredicated subtypes,
because they sometimes return e.g. Empty.
This patch adds some Ada 2022 features to the set children of
Ada.Containers.
Tested on x86_64-pc-linux-gnu, committed on trunk
gcc/ada/
* libgnat/a-cbhase.adb, libgnat/a-cbhase.ads,
libgnat/a-cborse.adb, libgnat/a-cborse.ads,
libgnat/a-cihase.adb, libgnat/a-cihase.ads,
In some cases when a legal allocator which defines a new subtype for the
allocated object occurs as part of a record component constraint
expression, the compiler would incorrectly reject the allocator.
Tested on x86_64-pc-linux-gnu, committed on trunk
gcc/ada/
* sem_ch4.adb
This patch corrects removes some code duplication within the GNAT
compiler.
Tested on x86_64-pc-linux-gnu, committed on trunk
gcc/ada/
* exp_util.adb (Remove_Side_Effects): Combine identical
branches.
* sem_attr.adb (Analyze_Attribute): Combine identical cases
Functional containers are now controlled. Update the documentation
accordingly.
Tested on x86_64-pc-linux-gnu, committed on trunk
gcc/ada/
* doc/gnat_rm/the_gnat_library.rst: Functional vectors, sets,
and maps are now controlled.
* gnat_rm.texi: Regenerate.diff --git
Add a new unbounded functional sequence. This sequence is indexed by
Big_Positive and so is unbounded from the user and spark points view.
Hower the actually implemented sequence are bounded by Count_Type'Last.
Tested on x86_64-pc-linux-gnu, committed on trunk
gcc/ada/
*
When resolving the Iterable aspect we look for a functions that are
declared in the same scope as the annotated type and that have the
required number and types formal parameters. However, we didn't guard
against functions that have no formal parameter at all.
Tested on x86_64-pc-linux-gnu,
This patch corrects an error in the compiler whereby the presence of a
call to a function returning a type with an access discriminant within
an expanded loop condition caused the wrong value to be supplied for the
extra- accessibility-of-result actual, thus causing incorrect checks
within the
The current wording can be read as implying that the result of a call
to a pure function does not depend on the context, which is incorrect.
The pragma only guarantees the absence of side effects of such a call.
Tested on x86_64-pc-linux-gnu, committed on trunk
gcc/ada/
*
When the result type of a function requiring built-in-place return is
only visible through a limited_with clause, the compiled needs to wait
for the nonlimited view to be available in order to compute whether
the built-in-place return is needed, and this comprises tagging the
function with the
Document a behavior change in r12-8546. Ok for wwwdocs?
---
htdocs/gcc-12/changes.html | 26 ++
1 file changed, 26 insertions(+)
diff --git a/htdocs/gcc-12/changes.html b/htdocs/gcc-12/changes.html
index ae03c3c6..ef957204 100644
--- a/htdocs/gcc-12/changes.html
+++
When autopar uses graphites canonicalize_loop_closed_ssa it fails to
check whether propagation is allowed and thus it ends up messing up
abnormal constraints.
Bootstrapped and tested on x86_64-unknown-linux-gnu, pushed.
2022-07-01 Richard Biener
PR tree-optimization/106055
*
The high part of the symbol address is invalid for the constant pool. In
function rs6000_cannot_force_const_mem, we already return true for
"HIGH with UNSPEC" rtx. During debug GCC, I found that
rs6000_cannot_force_const_mem is called for some other HIGH code rtx
expressions which also indicate
On Mon, 2022-07-04 at 14:25 +0800, Lulu Cheng wrote:
> > How do you think about the suggestion from Richard about a backport into
> > gcc-12 branch? Normally we don't backport behavior changes, but making
> > 12.1 the only exception seems compelling.
>
> I agree with you and Richard.
>
>
On Fri, Jul 1, 2022 at 5:59 PM Andrew Carlotti wrote:
>
> On Fri, Jul 01, 2022 at 08:42:15AM +0200, Richard Biener wrote:
> > On Thu, Jun 30, 2022 at 6:04 PM Andrew Carlotti via Gcc-patches
> > wrote:
> > > diff --git a/gcc/config/aarch64/aarch64-builtins.cc
> > >
On Fri, Jul 1, 2022 at 5:32 PM Martin Sebor wrote:
>
> On 7/1/22 08:01, Qing Zhao wrote:
> >
> >
> >> On Jul 1, 2022, at 8:59 AM, Jakub Jelinek wrote:
> >>
> >> On Fri, Jul 01, 2022 at 12:55:08PM +, Qing Zhao wrote:
> >>> If so, comparing to the current implemenation to have all the checking
Hi,
Gentle ping this:
https://gcc.gnu.org/pipermail/gcc-patches/2022-June/597020.html
Thanks.
On 22/6/2022 下午 4:26, HAO CHEN GUI wrote:
> Hi,
> This patch uses CC instead of CCFP for all BCD operations. Thus, infinite
> math flag has no impact on BCD operations. To support BCD overflow and
>
Hi,
Gentle ping this:
https://gcc.gnu.org/pipermail/gcc-patches/2022-June/597158.html
Thanks.
On 24/6/2022 上午 10:02, HAO CHEN GUI wrote:
> Hi,
> This patch implements optab f[min/max]_optab by xs[min/max]dp on rs6000.
> Tests show that outputs of xs[min/max]dp are consistent with the
Hi,
This patch fails TImode for all 128-bit logical operation expanders. So
TImode splits to two DI registers during expand. Potential optimizations can
be taken after expand pass. Originally, the TImode logical operations are
split after reload pass. It's too late. The test case illustrates it.
在 2022/7/3 上午11:06, Xi Ruoyao 写道:
On Sat, 2022-07-02 at 16:35 +0800, Lulu Cheng wrote:
在 2022/7/2 下午4:24, Xi Ruoyao 写道:
I'll commit the patch with the hook removed after another regtest on
loongarch64-linux-gnu. I just rebuilt the entire system on my
3A5000,
so I need some time to set it
On Mon, Jul 4, 2022 at 7:10 AM Jiang, Haochen wrote:
>
> Hi all,
>
> I revised my patch according to all your reviews.
>
> Regtested on x86_64-pc-linux-gnu.
OK.
Thanks,
Uros.
>
> BRs,
> Haochen
>
> > -Original Message-
> > From: Liu, Hongtao
> > Sent: Thursday, June 30, 2022 4:57 PM
>
On Fri, 1 Jul 2022, Martin Jambor wrote:
> Hi,
>
> As the testcase in PR 105860 shows, the code that tries to re-use the
> handled_component chains in SRA can be horribly confused by unions,
> where it thinks it has found a compatible structure under which it can
> chain the references, but in
95 matches
Mail list logo
