On Mon, Mar 06, 2023 at 11:27:16AM +0100, Robin Dapp wrote:
> > This broke the tests, I'm seeing syntax errors:
> > ERROR: gcc.dg/vect/slp-3.c -flto -ffat-lto-objects: error executing
> > dg-final: syntax error in target selector "target ! vect_partial_vectors
> > || vect32 || s390_vx"
> > ERRO
On Tue, 7 Mar 2023, Xionghu Luo wrote:
>
>
> On 2023/3/6 16:11, Richard Biener wrote:
> > On Mon, Mar 6, 2023 at 8:22 AM Xionghu Luo wrote:
> >>
> >>
> >>
> >> On 2023/3/2 18:45, Richard Biener wrote:
>
>
> small.gcno: 648: block 2:`small.c':1, 3, 4, 6
> >>>
Hi,
The patch escalates the failure when Hollerith constant to real conversion
fails in native_interpret_expr. It finally reports an "Cannot simplify
expression" error in do_simplify method.
The patch of pr95450 added a verification for decoding/encoding checking
in native_interpret_expr. nati
Hi!
In my recent rtti.cc change I assumed when emitting the support tinfos
that the tinfos for the fundamental types haven't been created yet.
Normally (in libsupc++.a (fundamental_type_info.o)) that is the case,
but as can be seen on the testcase, one can violate it by using typeid
etc. in the sa
According to https://github.com/riscv/riscv-bfloat16 , zfbfmin extension
depends on zfh/zfhmin extension.
According to the discussion
https://github.com/riscv-non-isa/riscv-elf-psabi-doc/pull/367, this use __bf16
and use DF16b in riscv_mangle_type like x86.
gcc\ChangeLog:
* com
On 2023/3/7 16:53, Richard Biener wrote:
On Tue, 7 Mar 2023, Xionghu Luo wrote:
Unfortunately this change (flag_test_coverage -> !optimize ) caused hundred
of gfortran cases execution failure with O0. Take gfortran.dg/index.f90 for
example:
.gimple:
__attribute__((fn spec (". ")))
void p
The following addresses PR109046 by adding an optimization to forwprop
to combine a piecewise complex load to a complex load when there are
no uses of the components. That's something useful in general and
easier to do than avoiding the splitting in complex lowering.
The testcase exercises both t
On Tue, 7 Mar 2023, Xionghu Luo wrote:
>
>
> On 2023/3/7 16:53, Richard Biener wrote:
> > On Tue, 7 Mar 2023, Xionghu Luo wrote:
>
> >> Unfortunately this change (flag_test_coverage -> !optimize ) caused hundred
> >> of gfortran cases execution failure with O0. Take gfortran.dg/index.f90
> >>
Hi Costas,
On 3/7/23 01:52, Costas Argyris via Gcc-patches wrote:
This is a proposal for addressing
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108865
by integrating the UTF-8 manifest file into gcc's build process for the
64-bit mingw host.
Is there a reason to make it specific to x86_64?
From: Pan Li
Fix the bug of the rvv bool mode precision with the adjustment.
The bits size of vbool*_t will be adjusted to
[1, 2, 4, 8, 16, 32, 64] according to the rvv spec 1.0 isa. The
adjusted mode precison of vbool*_t will help underlying pass to
make t
Great! Thank you very much for help, Richard Sandiford!
Just adjusted the PATCH v5 with minor changes for the GNU style check, and
completed the regression test and the RISC-V backend test without any surprise.
Given that is there anyone can help to merge this PATCH? Any question or
concern plea
On 06/03/23 23:11 +0100, Jannik Glückert wrote:
copy_file_range is a recent-ish syscall for copying files. It is similar
to sendfile but allows filesystem-specific optimizations. Common are:
Reflinks: BTRFS, XFS, ZFS (does not implement the syscall yet)
Server-side copy: NFS, SMB
If copy_file_ra
Hi Pan:
Really appreciate your patch for fixing this issue!
committed to trunk with minor commit log tweak :)
On Tue, Mar 7, 2023 at 8:05 PM pan2.li--- via Gcc-patches
wrote:
>
> From: Pan Li
>
> Fix the bug of the rvv bool mode precision with the adjustment.
> The bits size of
Hi Jacek,
"Is there a reason to make it specific to x86_64? It seems to me that all
mingw hosts could use it."
Are you referring to the 32-bit host?My concern here is that this
functionality (embedding the UTF-8
manifest file into the executable) is only truly supported in recent
versions of
Hi Costas,
On 3/7/23 15:00, Costas Argyris wrote:
Hi Jacek,
"Is there a reason to make it specific to x86_64? It seems to me that
all mingw hosts could use it."
Are you referring to the 32-bit host? My concern here is that this
functionality (embedding the UTF-8
manifest file into the ex
On 3/7/23 01:32, Hans-Peter Nilsson wrote:
>> From: Mike Stump
>> Date: Mon, 6 Mar 2023 02:05:35 -0800
>
>> Ok
>
> Thanks! The server-side hook didn't like my ChangeLog
> entry:
>
> * lib/multiline.exp (_build_multiline_regex): Map
> "{re:" to "(", ":re}" to ")" and ":r
On 3/6/23 16:54, Marek Polacek wrote:
On Fri, Mar 03, 2023 at 09:30:38PM -0500, Jason Merrill wrote:
On 3/3/23 12:50, Marek Polacek wrote:
switch (TREE_CODE (expr))
{
case CALL_EXPR:
@@ -13831,7 +13895,8 @@ do_warn_dangling_reference (tree expr)
std::pair v = std
On 3/6/23 17:01, Marek Polacek wrote:
On Mon, Mar 06, 2023 at 11:12:56AM -0500, Jason Merrill wrote:
On 3/3/23 12:51, Marek Polacek wrote:
Similarly to PR107938, this also started with r11-557, whereby cp_finish_decl
can call check_initializer even in a template for a constexpr initializer.
He
On 3/6/23 18:59, Marek Polacek wrote:
When processing a noexcept, constructors aren't elided: build_over_call
has
/* It's unsafe to elide the constructor when handling
a noexcept-expression, it may evaluate to the wrong
value (c++/53025). */
&& (force_el
Paul,
first of all, thank you very much indeed for the hard work you put into
this! This is a great step for gfortran.
I can hurry this along to get the patch
into 13-branch or I can wait until 14-branch opens.
Personally, I think that this fixes so many bugs, and makes
the compiler so much
On 3/7/23 04:07, Jakub Jelinek wrote:
Hi!
In my recent rtti.cc change I assumed when emitting the support tinfos
that the tinfos for the fundamental types haven't been created yet.
Normally (in libsupc++.a (fundamental_type_info.o)) that is the case,
but as can be seen on the testcase, one can v
On Tue, Mar 07, 2023 at 09:53:28AM -0500, Jason Merrill wrote:
> On 3/6/23 17:01, Marek Polacek wrote:
> > On Mon, Mar 06, 2023 at 11:12:56AM -0500, Jason Merrill wrote:
> > > On 3/3/23 12:51, Marek Polacek wrote:
> > > > Similarly to PR107938, this also started with r11-557, whereby
> > > > cp_fi
Hi Jacek,
"but I think it should work just fine if you didn't explicitly limit the
patch to x86_64."
I would think so too.
Actually, even cygwin might benefit from this, assuming it has the same
problem, which I don't know if it's the case.
But I'm not experienced with that so I would like to e
On Tue, Mar 07, 2023 at 03:58:32PM +0100, Thomas Koenig via Fortran wrote:
> Paul,
>
> first of all, thank you very much indeed for the hard work you put into
> this! This is a great step for gfortran.
Ditto**2
> > I can hurry this along to get the patch
> > into 13-branch or I can wait until 1
Tested powerpc64le-linux. Pushed to trunk.
-- >8 --
libstdc++-v3/ChangeLog:
* libsupc++/eh_personality.cc: Fix spelling in comment.
---
libstdc++-v3/libsupc++/eh_personality.cc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libstdc++-v3/libsupc++/eh_personality.cc
Tested powerpc64le-linux. Pushed to trunk.
-- >8 --
libstdc++-v3/ChangeLog:
PR libstdc++/108882
* config/abi/pre/gnu.ver (GLIBCXX_3.4.31): Adjust patterns to
not match symbols in namespace std::__gnu_cxx11_ieee128.
* config/os/gnu-linux/ldbl-ieee128-extra.ver: Add
Hi All,
When doing an emergency dump the cfg output dumps are corrupted because the
ending "}" is missing.
Normally when the pass manager finishes it would call finish_graph_dump_file to
produce this. This is called here because each pass can dump multiple digraphs.
However during an emergency
On Mon, 20 Feb 2023 at 11:54, Jakub Jelinek via Libstdc++
wrote:
>
> Hi!
Sorry for the delay.
> This updates baseline_symbols.txt for the Fedora 39 arches.
> Most of the added symbols are added to all 6 files, exceptions are
> DF16_ rtti stuff (only added on x86 and aarch64 which supports those)
On Mon, 6 Mar 2023 11:29:30 + (UTC)
Richard Biener via Gcc-patches wrote:
> On Mon, 6 Mar 2023, Jakub Jelinek wrote:
>
> > On Mon, Mar 06, 2023 at 11:01:18AM +, Richard Biener wrote:
> > > + auto_mpfr &operator=(const auto_mpfr &) = delete;
> > > + auto_mpz &operator=(const auto_mpz
On Tue, Mar 07, 2023 at 07:51:03PM +0100, Bernhard Reutner-Fischer wrote:
> While it's a nice idea, there have been resentments towards (visible)
> C++ in the fortran frontend and especially the library, i think.
I thought libgfortran is written in C and Fortran and doesn't use gmp/mpfr,
so this d
Hi,
On Mon, 6 Mar 2023, Richard Biener via Gcc-patches wrote:
> --- a/gcc/realmpfr.h
> +++ b/gcc/realmpfr.h
> @@ -24,6 +24,26 @@
> #include
> #include
>
> +class auto_mpfr
> +{
> +public:
> + auto_mpfr () { mpfr_init (m_mpfr); }
> + explicit auto_mpfr (mpfr_prec_t prec) { mpfr_init2 (m_mp
Tested x86_64-pc-linux-gnu, applying to trunk.
-- 8< --
A missed piece of the patch for static operator(): in tsubst_function_decl,
we don't want to replace the first parameter with a new closure pointer if
operator() is static.
PR c++/108526
PR c++/106651
gcc/cp/ChangeLog:
Hi, Jan,
I am studying one profiling feedback ICE bug with GCC8 recently.
It’s an assertion failure inside the routine “compute_working_sets”of gcov-io.c:
gcov_nonruntime_assert (ws_ix == NUM_GCOV_WORKING_SETS);
After some debugging and study, I found that the corresponding .gcda file has
two
ranges::begin() isn't guaranteed to be equality-preserving for
non-forward ranges, so in cartesian_product_view::end we need to be
careful about calling begin() on the first range (which could be
non-forward) in the (non-degenerate) case where __empty_tail is false.
Since we're already using a var
On Tue, 7 Mar 2023, Patrick Palka wrote:
> ranges::begin() isn't guaranteed to be equality-preserving for
> non-forward ranges, so in cartesian_product_view::end we need to be
> careful about calling begin() on the first range (which could be
> non-forward) in the (non-degenerate) case where __emp
On Tue, 7 Mar 2023 at 19:15, Alexander Monakov wrote:
>
> Hi,
>
> On Mon, 6 Mar 2023, Richard Biener via Gcc-patches wrote:
>
> > --- a/gcc/realmpfr.h
> > +++ b/gcc/realmpfr.h
> > @@ -24,6 +24,26 @@
> > #include
> > #include
> >
> > +class auto_mpfr
> > +{
> > +public:
> > + auto_mpfr () { mpf
On Tue, 7 Mar 2023, Jonathan Wakely wrote:
> > Shouldn't this use the idiom suggested in ansidecl.h, i.e.
> >
> > private:
> > DISABLE_COPY_AND_ASSIGN (auto_mpfr);
>
>
> Why? A macro like that (or a base class like boost::noncopyable) has
> some value in a code base that wants to work fo
Hello-
May I please ping this short patch that fixes an old bug? Thanks...
-Lewis
On Sat, Jan 14, 2023 at 1:46 PM Lewis Hyatt wrote:
>
> get__Pragma_string() in directives.cc is responsible for lexing the parens
> and the string argument from a _Pragma("...") operator. This function does
> not
On Tue, 7 Mar 2023 at 21:52, Alexander Monakov wrote:
>
>
> On Tue, 7 Mar 2023, Jonathan Wakely wrote:
>
> > > Shouldn't this use the idiom suggested in ansidecl.h, i.e.
> > >
> > > private:
> > > DISABLE_COPY_AND_ASSIGN (auto_mpfr);
> >
> >
> > Why? A macro like that (or a base class like bo
On Tue, Mar 07, 2023 at 09:54:08PM +, Jonathan Wakely via Gcc-patches wrote:
> On Tue, 7 Mar 2023 at 21:52, Alexander Monakov wrote:
> >
> >
> > On Tue, 7 Mar 2023, Jonathan Wakely wrote:
> >
> > > > Shouldn't this use the idiom suggested in ansidecl.h, i.e.
> > > >
> > > > private:
> > > >
On 3/1/23 05:53, Jonny Grant wrote:
Hello
I don't have write access, could someone review and apply this please?
Kind regards
Jonny
Looks good; I've gone ahead and pushed it for you.
-Sandra
On 1/11/23 07:57, Benson Muite via Gcc-patches wrote:
Improvement to documentation from a new contributor without commit rights.
On 1/5/23 06:38, Benson Muite wrote:
Link is missing from install documentation
Thanks, I've pushed this patch.
-Sandra
On 2/23/23 03:27, Arsen Arsenović via Gcc-patches wrote:
I've rerendered the updated documentation with latest development
Texinfo (as some of the changes I made for the purposes of the GCC
manual still aren't in releases) at:
https://www.aarsen.me/~arsen/final/
Ummm. I don't think GCC's d
Tested x86_64-pc-linux-gnu. Does this look good, or do we want to factor the
flag clearing into a symtab_node counterpart to cgraph_node::reset?
-- 8< --
In 107897, by the time we are looking at the mangling clash, the
alias has already been removed from the symbol table by analyze_functions,
so
From: Ju-Zhe Zhong
gcc/ChangeLog:
* config/riscv/riscv-vector-builtins-bases.cc: Split indexed load
patterns according to RVV ISA.
* config/riscv/vector-iterators.md: New iterators.
* config/riscv/vector.md
(@pred_indexed_load): Remove.
(@pred_indexed_load_same_
This series of patches adds foundational support for RISC-V auto-vectorization
support. These patches are based on the current upstream rvv vector intrinsic
support and is not a new implementation. Most of the implementation consists of
adding the new vector cost model, the autovectorization pat
2023-03-02 Michael Collison
Juzhe Zhong
* config/riscv/riscv-protos.h (riscv_classify_vlmul_field):
New external declaration.
(riscv_vector_preferred_simd_mode): Ditto.
(riscv_tuple_mode_p): Ditto.
(riscv_vector_mask_mode_p): Ditto.
2023-03-02 Michael Collison
Juzhe Zhong
* config/riscv/riscv-v.cc (riscv_classify_vlmul_field):
New function.
(riscv_vector_preferred_simd_mode): Ditto.
(get_mask_policy_no_pred): Ditto.
(get_tail_policy_no_pred): Ditto.
(riscv_tuple
2023-03-02 Michael Collison
Juzhe Zhong
* config/riscv/riscv-vector-builtins.cc (get_tail_policy_for_pred):
Remove static declaration to to make externally visible.
(get_mask_policy_for_pred): Ditto.
* config/riscv/riscv-vector-builtins.h (get_tail_
2023-03-02 Michael Collison
Juzhe Zhong
* config/riscv/riscv.cc (riscv_option_override):
Set riscv_vectorization_factor.
(riscv_estimated_poly_value): Implement
TARGET_ESTIMATED_POLY_VALUE.
(riscv_preferred_simd_mode): Implement
TARG
2023-03-02 Michael Collison
Juzhe Zhong
* config/riscv/riscv.md (riscv_vector_preferred_simd_mode): Include
vector-iterators.md.
* config/riscv/vector-auto.md: New file containing
autovectorization patterns.
* config/riscv/vector-iterators.m
2023-03-02 Michael Collison
Vineet Gupta
* gcc.target/riscv/rvv/autovec: New directory
for autovectorization tests.
* gcc.target/riscv/rvv/autovec/loop-add-rv32.c: New
test to verify code generation of vector add on rv32.
* gcc.target/riscv/r
Committed as obvious.
-- >8 --
The recently added tests missed checking for "fopenmp" (see
other tests where "-fopenmp" is passed), which makes them
fail on non-openmp systems.
* gcc.dg/analyzer/omp-parallel-for-get-min.c,
gcc.dg/analyzer/omp-parallel-for-1.c: Require effective tar
The mips msa-ds.c test is trying to ensure that MSA branches can have
their delay slots filled. The regexp it used looked for the function
name, a nop, then the function name again. If found that sequence, then
the test failed.
The problem is with Vlad's recent IRA work there's simply less
This patch makes LRA well with some exceptions
(e.g. MI thunk generation due to pretending reload_completed).
gcc/ChangeLog:
* config/xtensa/constraints.md (R, T, U):
Change define_constraint to define_memory_constraint.
* config/xtensa/xtensa.cc (xtensa_legitimate_constan
From: Ju-Zhe Zhong
gcc/ChangeLog:
* config/riscv/vector-iterators.md (=vd,vr): Fine tune.
(=vd,vd,vr,vr): Ditto.
* config/riscv/vector.md: Ditto.
gcc/testsuite/ChangeLog:
* gcc.target/riscv/rvv/base/merge_constraint-2.c: New test.
---
gcc/config/riscv/vector-i
> Thanks, I've pushed this patch.
>
> -Sandra
Appreciated. Thanks.
Hi,
When OMP_WAIT_POLICY is not specified, current implementation will cause
icv flag GOMP_ICV_WAIT_POLICY unset, so global variable wait_policy
will remain its uninitialized value. Set it to -1 when the flag is not
specified to keep GOMP_SPINCOUNT behavior consistent with its description.
Bootst
On Tue, 7 Mar 2023, Tamar Christina wrote:
> Hi All,
>
> When doing an emergency dump the cfg output dumps are corrupted because the
> ending "}" is missing.
>
> Normally when the pass manager finishes it would call finish_graph_dump_file
> to
> produce this. This is called here because each p
On Wed, 8 Mar 2023, Alexander Monakov wrote:
>
> On Tue, 7 Mar 2023, Jonathan Wakely wrote:
>
> > > Shouldn't this use the idiom suggested in ansidecl.h, i.e.
> > >
> > > private:
> > > DISABLE_COPY_AND_ASSIGN (auto_mpfr);
> >
> >
> > Why? A macro like that (or a base class like boost::n
From: yes
Fix the bug of the rvv bool mode size by the adjustment.
Besides the mode precision (aka bit size [1, 2, 4, 8, 16, 32, 64])
of the vbool*_t, the mode size (aka byte size) will be adjusted to
[1, 1, 1, 1, 2, 4, 8] according to the rvv spec 1.0 isa. The
adjustment will provide correct inf
On Wed, Mar 08, 2023 at 02:31:38PM +0800, Hongyu Wang wrote:
> Hi,
>
> When OMP_WAIT_POLICY is not specified, current implementation will cause
> icv flag GOMP_ICV_WAIT_POLICY unset, so global variable wait_policy
> will remain its uninitialized value. Set it to -1 when the flag is not
> specified
From: Ju-Zhe Zhong
Hi, current maybe_gen_insn can only expand 9 nops.
For RVV intrinsics, I need to extend it as 10, otherwise I should use GEN_FCN.
This patch is quite obvious change, Ok for trunk ?
Thanks.
gcc/ChangeLog:
* config/riscv/riscv-vector-builtins.cc
(function_expander::us
On Wed, 8 Mar 2023, juzhe.zh...@rivai.ai wrote:
> From: Ju-Zhe Zhong
>
> Hi, current maybe_gen_insn can only expand 9 nops.
> For RVV intrinsics, I need to extend it as 10, otherwise I should use GEN_FCN.
> This patch is quite obvious change, Ok for trunk ?
The optabs.cc change is OK.
Thanks,
64 matches
Mail list logo
