Bit manipulation extension[1] is finishing the public review and waiting for
the rest of the ratification process, I believe that will become a ratified
extension soon, so I think it's time to submit to upstream for review now :)
As the title included RFC, it's not a rush to merge to trunk yet, I
2021-09-23 Kito Cheng
gcc/ChangeLog:
* common/config/riscv/riscv-common.c (riscv_ext_version_table):
Add zba, zbb, zbc and zbs.
(riscv_ext_flag_table): Ditto.
* config/riscv/riscv-opts.h (MASK_ZBA): New.
(MASK_ZBB): Ditto.
(MASK_ZBC): Ditto.
From: Jim Wilson
2021-09-23 Jim Wilson
Kito Cheng
Jia-Wei Chen
gcc/ChangeLog:
* config/riscv/bitmanip.md (*zero_extendsidi2_bitmanip): New.
(*shNadd): Ditto.
(*shNadduw): Ditto.
(*add.uw): Ditto.
(*slliuw): Ditto.
* config
2021-09-23 Kito Cheng
gcc/ChangeLog:
* config/riscv/riscv.c (riscv_extend_cost): Handle cost model
for zba extension.
(riscv_rtx_costs): Ditto.
---
gcc/config/riscv/riscv.c | 81
1 file changed, 81 insertions(+)
diff --git a/gcc/
From: Jim Wilson
2021-09-23 Jim Wilson
Kito Cheng
Jia-Wei Chen
gcc/ChangeLog:
* config/riscv/bitmanip.md (bitmanip_bitwise): New.
(bitmanip_minmax): New.
(clz_ctz_pcnt): New.
(bitmanip_optab): New.
(bitmanip_insn): New.
(*
2021-09-23 Kito Cheng
gcc/ChangeLog:
* config/riscv/riscv.c (riscv_extend_cost): Handle cost model
for zbb extension.
(riscv_rtx_costs): Ditto.
---
gcc/config/riscv/riscv.c | 17 +
1 file changed, 17 insertions(+)
diff --git a/gcc/config/riscv/riscv.c b/
From: Jim Wilson
gcc/ChangeLog:
* config/riscv/riscv.c (riscv_build_integer_1): Build integer
with rotate.
gcc/testsuite/ChangeLog:
* gcc.target/riscv/zbb-li-rotr.c: New.
---
gcc/config/riscv/riscv.c | 41
gcc/testsuite/gcc.targ
From: Jim Wilson
2021-09-23 Jim Wilson
Kito Cheng
gcc/ChangeLog:
* config/riscv/bitmanip.md (shiftm1): New.
(*bset): Ditto.
(*bset_mask): Ditto.
(*bset_1): Ditto.
(*bset_1_mask): Ditto.
(*bseti): Ditto.
(*bclr): Ditto.
2021-09-23 Kito Cheng
gcc/ChangeLog:
* config/riscv/riscv.c (riscv_rtx_costs): Handle cost model
for zbs extension.
---
gcc/config/riscv/riscv.c | 47
1 file changed, 47 insertions(+)
diff --git a/gcc/config/riscv/riscv.c b/gcc/config/ri
Hi!
If omp::directive attribute argument starting with the opening ( is not a
balanced
token sequence, then cp_parser_skip_balanced_tokens (parser, 1) returns 1,
but the code was subtracting 2 from it and iterating until it was 0, so for the
non-balanced case it iterated from (size_t) -1 down to
On Thu, Sep 23, 2021 at 3:09 AM Feng Xue OS via Gcc-patches
wrote:
>
> Bootstrapped/regtested on x86_64-linux and aarch64-linux.
OK for trunk and all affected branches.
Thanks,
Richard.
> Thanks,
> Feng
>
> ---
> 2021-09-23 Feng Xue
>
> gcc/ChangeLog:
> PR tree-optimization/102451
>
On Thu, Sep 23, 2021 at 3:24 AM Feng Xue OS via Gcc-patches
wrote:
>
> Bootstrapped/regtested on x86_64-linux.
OK for all affected branches.
Thanks,
Richard.
> Thanks,
> Feng
> ---
> 2021-09-23 Feng Xue
>
> gcc/ChangeLog
> PR tree-optimization/102400
> * tree-ssa-sccvn.c (vn_
On Wed, Sep 22, 2021 at 5:47 PM Andrew Burgess
wrote:
>
> The top-level configure script is shared between the gcc repository
> and the binutils-gdb repository.
>
> The target_configdirs variable in the configure.ac script, defines
> sub-directories that contain components that should be built for
Hi,
This patch extend the expanders for cond_op to support vector HF modes.
bootstraped and regtested on x86_64-pc-linux-gnu{-m32,}.
Ok for master?
gcc/ChangeLog:
* config/i386/sse.md (cond_): Extend to support
vector HFmodes.
(cond_mul): Likewise.
(cond_div): Lik
This fixes the previous change which removed setting alignment info
from the vectorizers idea of how a pointer is being used but left
in place the copied info from DR_PTR_INFO without realizing that this
is in fact _not_ the alignment of the access but the alignment of
a base pointer contained in i
Hi!
I only had a curious look here; hope that's still useful.
On 2021-09-22T16:30:42+0100, Andrew Burgess wrote:
> The top-level configure script is shared between the gcc repository
> and the binutils-gdb repository.
>
> The target_configdirs variable in the configure.ac script, defines
> sub-d
>-Original Message-
>From: Wang, Hongyu
>Sent: Thursday, September 23, 2021 5:16 PM
>To: Liu, Hongtao
>Cc: gcc-patches@gcc.gnu.org
>Subject: [PATCH] AVX512FP16: Support cond_op for HFmode
>
>Hi,
>
>This patch extend the expanders for cond_op to support vector HF modes.
>bootstraped and
> On 22/09/2021 03:10 Luís Ferreira wrote:
>
>
> Currently a stack/heap overflow may happen if a crafted mangle is
> maliciously used to cause denial of service, such as intentional
> crashes
> by accessing a reserved memory space.
>
Hi,
Thanks for this. Is there a test that could trigger t
> On 22/09/2021 03:31 Luís Ferreira wrote:
>
>
> This patch prevents dereferencing a null reference on a crafted
> malformed magled name, often causing SIGSEGV to be raised.
>
OK, seems reasonable to me.
> Signed-off-by: Luís Ferreira
> ---
> libiberty/d-demangle.c | 2 +-
On Wed, 22 Sept 2021 at 18:56, Antony Polukhin wrote:
>
> ср, 22 сент. 2021 г. в 20:44, Jonathan Wakely :
> >
> > On Wed, 22 Sept 2021 at 18:09, Antony Polukhin wrote:
> > >
> > > std::unique_ptr allows construction from std::unique_ptr of derived
> > > type as per [unique.ptr.single.asgn] and [un
On 16/09/21 15:41 +0100, Jonathan Wakely wrote:
The https://gcc.gnu.org/git.html page is a total mess, listing dozens
and dozens of branches which haven't seen updates in a decade and
which are under the refs/dead/heads/* are of the Git repo.
This moves them all to the "Inactive" or "Merged" sec
On Wed, 22 Sept 2021 at 23:19, Jim Wilson wrote:
> On Fri, Sep 17, 2021 at 4:39 AM Jonathan Wakely via Gcc-patches <
> gcc-patches@gcc.gnu.org> wrote:
>
>> The list of architectures that support the option is incomplete.
>>
>> gcc/ChangeLog:
>>
>> * configure.ac: Fix --with-multilib-list d
On Thu, 23 Sept 2021 at 11:36, Jonathan Wakely wrote:
> On Wed, 22 Sept 2021 at 23:19, Jim Wilson wrote:
>
>> On Fri, Sep 17, 2021 at 4:39 AM Jonathan Wakely via Gcc-patches <
>> gcc-patches@gcc.gnu.org> wrote:
>>
>>> The list of architectures that support the option is incomplete.
>>>
>>> gcc/Cha
Hello Jeff,
>I would strongly recommend removing all the documentation related to
>single tree builds.
Two questions:
(1) When you say "all", are you suggesting that in-the-gcc-tree builds of gmp,
mpfr, mpc, and isl should no longer be documented? Or only in-tree builds of
binutils
On 9/22/21 10:05 AM, Richard Biener wrote:
On Tue, Sep 21, 2021 at 7:17 PM Aldy Hernandez via Gcc-patches
wrote:
On 9/21/21 7:05 PM, Andrew MacLeod wrote:
On 9/21/21 12:53 PM, Aldy Hernandez wrote:
SCEV won't work without dominators and we can get called without
dominators from debug_ran
On Thu, Sep 23, 2021 at 12:28 PM Jonathan Wakely via Gcc-patches
wrote:
>
> On 16/09/21 15:41 +0100, Jonathan Wakely wrote:
> >The https://gcc.gnu.org/git.html page is a total mess, listing dozens
> >and dozens of branches which haven't seen updates in a decade and
> >which are under the refs/dead
My upcoming improvements to the forward jump threader make it thread
more aggressively. In investigating some "regressions", I noticed
that it has always allowed threading through empty latches and across
loop boundaries. As we have discussed recently, this should be avoided
until after loop opti
On Wed, 22 Sep 2021, Ilya Leoshkevich wrote:
> PR tree-optimization/49749 introduced code that shortens dependency
> chains containing loop accumulators by placing them last on operand
> lists of associative operations.
>
> 456.hmmer benchmark on s390 could benefit from this, however, the code
>
On Wed, 22 Sep 2021, Ilya Leoshkevich wrote:
> Biasing loop-carried PHIs during the 1st reassociation pass interferes
> with reduction chains and does not bring measurable benefits, so do it
> only during the 2nd reassociation pass.
OK.
Thanks,
Richard.
> gcc/ChangeLog:
>
> * passe
On Wed, 22 Sep 2021, Ilya Leoshkevich wrote:
> Add both positive and negative tests.
OK I guess (you might want to check with -ftree-vectorize given
that's going to be enabled at -O2)
Richard.
> gcc/testsuite/ChangeLog:
>
> * gcc.dg/tree-ssa/reassoc-46.c: New test.
> * gcc.dg/tree-
On Wed, 22 Sep 2021, Hongtao Liu wrote:
> On Tue, Sep 21, 2021 at 10:55 PM H.J. Lu wrote:
> >
> > On Mon, Sep 20, 2021 at 5:15 AM Richard Biener via Gcc-patches
> > wrote:
> > >
> > > This allows vectorization (in practice non-loop vectorization) to
> > > have a stmt participate in different vec
On Wed, 22 Sep 2021, Xionghu Luo wrote:
>
>
> On 2021/8/11 17:16, Richard Biener wrote:
> > On Wed, 11 Aug 2021, Xionghu Luo wrote:
> >
> >>
> >>
> >> On 2021/8/10 22:47, Richard Biener wrote:
> >>> On Mon, 9 Aug 2021, Xionghu Luo wrote:
> >>>
> Thanks,
>
> On 2021/8/6 19:46, Ric
Hi Segher,
Thanks for the review! This is what I committed.
2021-09-23 Bill Schmidt
gcc/
PR target/102024
* config/rs6000/rs6000-call.c (rs6000_aggregate_candidate): Detect
zero-width bit fields and return indicator.
(rs6000_discover_homogeneous_aggregate): Di
The predefined Ada.Strings.Bounded unit has been annotated SPARK
contracts that reference a local constant:
generic
Max : Positive;
package Generic_Bounded_Length
Max_Length : constant Positive := Max;
function XXX return YYY with Global => Max_Length;
...
When this
Ada RM M.2 gives a list of implementation-defined characteristics, each
of which is required to be documented. This requirement is addressed in
the "Implementation Defined Characteristics" section of the GNAT RM.
This section needs to be updated to reflect changes to the Ada RM M.2
over the last fe
Replace use of SPARK_Mode Off on callers of procedure Move by stronger
preconditions, as mandated by Ada RM A.4.3, so that calls to the
corresponding functions inside the procedure bodies are provably
correct.
Tested on x86_64-pc-linux-gnu, committed on trunk
gcc/ada/
* libgnat/a-strfix.
SPARK rules regarding constants with variable inputs and generic actual
parameters are currently not flexible enough to allow an explicit
Initializes contract on Ada.Strings.Bounded.Generic_Bounded_Length.
This patch removes the explicit contract, so that GNATprove generates an
implicit one with o
This patch implements some efficiency improvements related to field
getters and setters, and implements some cleanups that make the
efficiency improvements easier.
Instead of just storing the Offset with each node, we store a node
header, which contains the Offset plus a small number of slots. Fie
When unnesting, we may add static links to the actual parameters. This
will cause duplication if a the Parameter_Associations list is shared,
so ensure that we make a new one in this situation.
Tested on x86_64-pc-linux-gnu, committed on trunk
gcc/ada/
* atree.adb (Relocate_Node): If rel
This patch improves compiler efficiency by placing the Homonym attribute
at offset zero. Homonym is a heavily used field.
Tested on x86_64-pc-linux-gnu, committed on trunk
gcc/ada/
* gen_il-gen.adb: Set the number of concrete nodes that have the
Homonym field to a higher number t
In Resolve_Array_Aggregate we typically compute and set Aggregate_Bounds
based on the aggregate itself. We only need to keep the already computed
bounds for aggregates that have been optimized into positional ones.
However, we kept the already computed bounds for other aggregates too.
In particula
This patch implements the two-pass algorithm described in RM 4.3.3
(20.2/5), for the construction of an array aggregate all of whose
component associations are iterated component associations with iterator
specifications. Each iterator specification is executed twice: once to
compute the number of
This documents the new --load option and makes a few minor tweaks.
Tested on x86_64-pc-linux-gnu, committed on trunk
gcc/ada/
* doc/gnat_ugn/gnat_utility_programs.rst (gnatsymbolize):
Document new --load option and -g1 as minimal compilation
requirement.diff --git a/gcc/a
This patch fixes decoration of wrappers of access to subprograms with
pre/post conditions (that is, wrappers internally built by the compiler
to support AI12-0220). This patch also adds assertions, fixes node
decorations, and avoids cascade errors.
Tested on x86_64-pc-linux-gnu, committed on trunk
Although 0 is not an errno value, it should still be recognized as
corresponding to a value belonging to the generic_category().
Signed-off-by: Jonathan Wakely
libstdc++-v3/ChangeLog:
PR libstdc++/102425
* src/c++11/system_error.cc
(system_error_category::default_error_c
Although 0 is not an errno value, it should still be recognized as
corresponding to a value belonging to the generic_category().
Signed-off-by: Jonathan Wakely
libstdc++-v3/ChangeLog:
PR libstdc++/102425
* src/c++11/system_error.cc
(system_error_category::default_error_c
This ensures that the objects returned by std::generic_category() and
std::system_category() are initialized before any code starts executing,
and are not destroyed at the end of the program. This means it is always
safe to access them, even during startup and termination. See LWG 2992
and P1195R0
The std::system_category error category should be used for
system-specific error codes, which means on Windows it should be used
for Windows error codes. Currently that category assumes that the error
numbers it deals with are errno numbers, which means that
ERROR_ACCESS_DENIED (which has value 0x
This test tries to ensure that can be included after
defining _XOPEN_SOURCE=600, which doesn't test anything if that header
is already included via the PCH before the macro
definition. Disable PCH so that it behaves as intended.
Signed-off-by: Jonathan Wakely
libstdc++-v3/ChangeLog:
*
I added extra dg-error directives for C++20 to match the extra errors
caused by some of the call stack being constexpr in C++20. Since Jason's
changes to reduce those errors, those dg-error lines no longer match.
This removes them again.
Signed-off-by: Jonathan Wakely
libstdc++-v3/ChangeLog:
On 9/23/21 12:30 AM, Richard Biener wrote:
On Thu, 23 Sep 2021, Hongtao Liu wrote:
On Thu, Sep 23, 2021 at 9:48 AM Hongtao Liu wrote:
On Wed, Sep 22, 2021 at 10:21 PM Martin Sebor wrote:
On 9/21/21 7:38 PM, Hongtao Liu wrote:
On Mon, Sep 20, 2021 at 4:13 AM Martin Sebor wrote:
...
dif
Hi,
Here is an example of a crafted mangle that can cause heap buffer
overflow.
```
fuzzer-results/crash-18b7f0799be49886550876b5ab6bb63e4231979b
_D2FGWG4EQe
5f 44 32 46 47 57 47 34 34 34 34 34 34 34 34 34
|_D2FGWG4|
0010 34 34 34 34 34 34 34 34 45 51 65
On 9/23/2021 4:16 AM, ibuclaw--- via Gcc-patches wrote:
On 22/09/2021 03:10 Luís Ferreira wrote:
Currently a stack/heap overflow may happen if a crafted mangle is
maliciously used to cause denial of service, such as intentional
crashes
by accessing a reserved memory space.
Hi,
Thanks
This patch is for PR101320, another issue related to missing bind(c)
diagnostics. OK to commit?
-Sandra
commit d3507154fd34e65e2887262218fec09d5fb082a2
Author: Sandra Loosemore
Date: Thu Sep 23 08:03:52 2021 -0700
Fortran: Diagnose default-initialized pointer/allocatable dummies
On 9/23/2021 4:17 AM, ibuclaw--- via Gcc-patches wrote:
On 22/09/2021 03:31 Luís Ferreira wrote:
This patch prevents dereferencing a null reference on a crafted
malformed magled name, often causing SIGSEGV to be raised.
OK, seems reasonable to me.
I pushed this to the trunk.
Thanks,
On 23.09.21 17:50, Sandra Loosemore wrote:
This patch is for PR101320, another issue related to missing bind(c)
diagnostics. OK to commit?
LGTM - I am only ...
commit d3507154fd34e65e2887262218fec09d5fb082a2
Author: Sandra Loosemore
Date: Thu Sep 23 08:03:52 2021 -0700
Fortran: Diagnos
On 9/23/2021 5:15 AM, Aldy Hernandez wrote:
My upcoming improvements to the forward jump threader make it thread
more aggressively. In investigating some "regressions", I noticed
that it has always allowed threading through empty latches and across
loop boundaries. As we have discussed recen
Clang implements something we don't have:
__attribute__((deprecated("message", "replacement")));
which seems pretty neat so I wrote this patch to add it to gcc.
It doesn't allow the optional second argument in the standard [[]]
form so as not to clash with possible future standard additions.
I
On 9/23/21 10:10 AM, Tobias Burnus wrote:
On 23.09.21 17:50, Sandra Loosemore wrote:
This patch is for PR101320, another issue related to missing bind(c)
diagnostics. OK to commit?
LGTM - I am only ...
diff --git a/gcc/fortran/decl.c b/gcc/fortran/decl.c
index f2e8896..b3c65b7 100644
--- a/gc
Hi Harald,
On 22.09.21 21:47, Harald Anlauf via Fortran wrote:
while still feeling somewhat unsure (given my previous comment
and the discussion), I think your patch is basically OK.
However, your testcase has a { dg-do compile }, so it does not
really do any runtime tests. Is that intended?
On 23.09.21 18:30, Sandra Loosemore wrote:
On 9/23/21 10:10 AM, Tobias Burnus wrote:
On 23.09.21 17:50, Sandra Loosemore wrote:
This patch is for PR101320, another issue related to missing bind(c)
diagnostics. OK to commit?
LGTM - I am only ...
+ gfc_error ("Default-initialized %s d
Hi,
The code handling various cases which lead to call graph edge
duplication (in order to update reference descriptions used to track
and remove no-longer needed references) has missed one important case.
When edge duplication is an effect of creating a speculative edge for
an indirect edge whic
This patch converts the Ranger ecosystem to use a local edge flag to
represent a "not executable" edge rather than reusing the
EDGE_EXECUTABLE flag.
This has multiple benefits,
- No need to set all the flags on every edge before starting
- No chance of interference from other passes which mig
The routnie that is trapping (relation_fold_and_or) is looking to see
if there are any relationships between dependencies that can be
exploited. ie
c_2 = a_6 > b_7
c_3 = a_6 < b_7
c_4 = c_2 && c_3
if (c_4 != 0)
when trying to fold c_4, it looks at c_2 and c_3, it notes that they
b
I'm past this snag, so disregard this RFC for now. If I post again about
this, it will be with a working patch.
On Fri, Sep 17, 2021 at 11:15 AM Barrett Adair
wrote:
> The WIP attached patch attempts to enable usage of parameters' constexpr
> members before the function body begins (see new test
From: Thomas Rodgers
This change implements P0528 which requires that padding bits not
participate in atomic compare exchange operations. All arguments to the
generic template are 'sanitized' by the __builtin_clear_padding intrinsic
before they are used in atomic compare_exchange. This alrequires
On 9/20/21 18:59, Marek Polacek via Gcc-patches wrote:
On Mon, Sep 20, 2021 at 09:08:09PM +0200, Jakub Jelinek wrote:
On Mon, Sep 20, 2021 at 02:37:03PM -0400, Marek Polacek wrote:
So, wouldn't be this better specified as
Wno-attributes=
Common Joined RejectNegative
(not sure if RejectNegative
On Thu, Sep 23, 2021 at 11:08:37AM -0700, Thomas Rodgers wrote:
> From: Thomas Rodgers
>
> This change implements P0528 which requires that padding bits not
> participate in atomic compare exchange operations. All arguments to the
Thanks for working on this.
> generic template are 'sanitized' b
On 20.09.21 09:58, Tobias Burnus wrote:
On 20.09.21 06:01, Sandra Loosemore wrote:
This patch fixes some bugs in handling of assumed-rank arguments
revealed by the TS29113 testsuite, ... giving a bogus error when
passing one as the first argument to the ASSOCIATED intrinsic. ...
... if I tr
Dear Fortranners,
we missed certain intrinsics as being disallowed in constant expressions,
which lead to an ICE when these intrinsics were used in a specification
expression with an initializer. The intrinsics in question are listed in
F2018:10.1.2.
As discussed in the PR, Steve recommended to
Am Mittwoch, den 22.09.2021, 17:18 -0400 schrieb Jason Merrill:
> On 9/5/21 15:14, Uecker, Martin wrote:
> > Here is the third version of the patch. This also
> > fixes the index zero case. Thus, this should be
> > a complete fix for 91038 and should fix all cases
> > also supported by clang. Sti
Agreed, I'll revise the patch to do so.
On Thu, Sep 23, 2021 at 12:07 PM Jakub Jelinek wrote:
> On Thu, Sep 23, 2021 at 11:08:37AM -0700, Thomas Rodgers wrote:
> > From: Thomas Rodgers
> >
> > This change implements P0528 which requires that padding bits not
> > participate in atomic compare ex
On Thu, 23 Sep 2021, 20:07 Jakub Jelinek via Libstdc++, <
libstd...@gcc.gnu.org> wrote:
> On Thu, Sep 23, 2021 at 11:08:37AM -0700, Thomas Rodgers wrote:
> > From: Thomas Rodgers
> >
> > This change implements P0528 which requires that padding bits not
> > participate in atomic compare exchange o
On Wed, Sep 22, 2021 at 7:05 PM Michel Morin wrote:
On Thu, Sep 23, 2021 at 5:09 AM Jason Merrill wrote:
>
> On 9/21/21 20:53, Michel Morin wrote:
> > On Tue, Sep 21, 2021 at 5:24 AM Jason Merrill
wrote:
> >>
> >> On 9/17/21 13:31, Michel Morin wrote:
> >>> On Fri
On Thu, 23 Sep 2021, liuhongt via Gcc-patches wrote:
> +IA-32/x86-64
> +
> + New ISA extension support for Intel AVX512-FP16 was added to GCC.
> + AVX512FP16 intrinsics are available via the -mavx512fp16
> + compiler switch.
> +
I think the support for _Float16 should be mentioned in t
In encode_ieee_double/quad, the assignment
unsigned long VAL = r->sign << 31;
is intended to set the 31st bit of VAL whenever the given REAL_CST is
negative. But on LP64 hosts it also unintentionally sets the upper 32
bits of VAL due to the promotion of r->sign from unsigned:1 to int and
the s
On 9/23/21 15:49, Uecker, Martin wrote:
Am Mittwoch, den 22.09.2021, 17:18 -0400 schrieb Jason Merrill:
On 9/5/21 15:14, Uecker, Martin wrote:
Here is the third version of the patch. This also
fixes the index zero case. Thus, this should be
a complete fix for 91038 and should fix all cases
als
Here's another missing-diagnostic patch for the Fortran front end, this
time for PR Fortran/101333. OK to commit?
-Sandra
commit 53171e748e28901693ca4362ff658883dab97e13
Author: Sandra Loosemore
Date: Thu Sep 23 15:00:43 2021 -0700
Fortran: Add missing diagnostic for F2018 C711 (TS29113
On Fri, Sep 24, 2021 at 5:29 AM Jason Merrill wrote:
>
> On Wed, Sep 22, 2021 at 7:05 PM Michel Morin wrote:
>
> On Thu, Sep 23, 2021 at 5:09 AM Jason Merrill wrote:
> >
> > On 9/21/21 20:53, Michel Morin wrote:
> > > On Tue, Sep 21, 2021 at 5:24 AM Jason Merrill
> wrote:
Harald,
Looks good. OK and thanks for your time and efforts.
Jerry
On 9/23/21 12:47 PM, Harald Anlauf via Fortran wrote:
Dear Fortranners,
we missed certain intrinsics as being disallowed in constant expressions,
which lead to an ICE when these intrinsics were used in a specification
expressi
Updated, mention _Float16 support.
---
htdocs/gcc-12/changes.html | 13 -
1 file changed, 12 insertions(+), 1 deletion(-)
diff --git a/htdocs/gcc-12/changes.html b/htdocs/gcc-12/changes.html
index 81f62fe3..f19c6718 100644
--- a/htdocs/gcc-12/changes.html
+++ b/htdocs/gcc-12/changes.
On Thu, Sep 23, 2021 at 6:17 PM liuhongt wrote:
>
> Updated, mention _Float16 support.
>
> ---
> htdocs/gcc-12/changes.html | 13 -
> 1 file changed, 12 insertions(+), 1 deletion(-)
>
> diff --git a/htdocs/gcc-12/changes.html b/htdocs/gcc-12/changes.html
> index 81f62fe3..f19c6718 100
On Fri, Sep 24, 2021 at 9:20 AM H.J. Lu wrote:
>
> On Thu, Sep 23, 2021 at 6:17 PM liuhongt wrote:
> >
> > Updated, mention _Float16 support.
> >
> > ---
> > htdocs/gcc-12/changes.html | 13 -
> > 1 file changed, 12 insertions(+), 1 deletion(-)
> >
> > diff --git a/htdocs/gcc-12/chan
On Thu, Sep 23, 2021 at 6:38 PM Hongtao Liu wrote:
>
> On Fri, Sep 24, 2021 at 9:20 AM H.J. Lu wrote:
> >
> > On Thu, Sep 23, 2021 at 6:17 PM liuhongt wrote:
> > >
> > > Updated, mention _Float16 support.
> > >
> > > ---
> > > htdocs/gcc-12/changes.html | 13 -
> > > 1 file changed,
On Fri, Sep 24, 2021 at 9:42 AM H.J. Lu wrote:
>
> On Thu, Sep 23, 2021 at 6:38 PM Hongtao Liu wrote:
> >
> > On Fri, Sep 24, 2021 at 9:20 AM H.J. Lu wrote:
> > >
> > > On Thu, Sep 23, 2021 at 6:17 PM liuhongt wrote:
> > > >
> > > > Updated, mention _Float16 support.
> > > >
> > > > ---
> > > >
On Thu, Sep 23, 2021 at 6:58 PM Hongtao Liu wrote:
>
> On Fri, Sep 24, 2021 at 9:42 AM H.J. Lu wrote:
> >
> > On Thu, Sep 23, 2021 at 6:38 PM Hongtao Liu wrote:
> > >
> > > On Fri, Sep 24, 2021 at 9:20 AM H.J. Lu wrote:
> > > >
> > > > On Thu, Sep 23, 2021 at 6:17 PM liuhongt wrote:
> > > > >
> >This patch extend the expanders for cond_op to support vector HF modes.
> >bootstraped and regtested on x86_64-pc-linux-gnu{-m32,}.
> Do runtime tests passe on sde{-m32,}?
Yes, forgot to mention this.
Liu, Hongtao via Gcc-patches 于2021年9月23日周四 下午5:31写道：
>
>
>
> >-Original Message-
>
On Fri, Sep 24, 2021 at 10:16 AM Hongyu Wang via Gcc-patches
wrote:
>
> > >This patch extend the expanders for cond_op to support vector HF modes.
> > >bootstraped and regtested on x86_64-pc-linux-gnu{-m32,}.
> > Do runtime tests passe on sde{-m32,}?
>
> Yes, forgot to mention this.
>
> Liu, Hongt
On Thu, Sep 23, 2021 at 11:18 PM Martin Sebor wrote:
>
> On 9/23/21 12:30 AM, Richard Biener wrote:
> > On Thu, 23 Sep 2021, Hongtao Liu wrote:
> >
> >> On Thu, Sep 23, 2021 at 9:48 AM Hongtao Liu wrote:
> >>>
> >>> On Wed, Sep 22, 2021 at 10:21 PM Martin Sebor wrote:
>
> On 9/21/21 7:
Update the patch to v3, not sure whether you prefer the paste style
and continue to link the previous thread as Segher dislikes this...
[PATCH v3] Don't move cold code out of loop by checking bb count
Changes:
1. Handle max_loop in determine_max_movement instead of
outermost_invariant_loop.
2.
90 matches
Mail list logo
