Fixes the following clang warning:
gcc/gimple-range-op.cc:310:16: warning: 'fold_range' overrides a member
function but is not marked 'override' [-Winconsistent-missing-override]
gcc/ChangeLog:
* gimple-range-op.cc: Add override keyword.
---
gcc/gimple-range-op.cc | 2 +-
1 file changed
On Mon, Oct 10, 2022 at 4:12 PM Paul Iannetta via Gcc-patches
wrote:
>
> Hi,
>
> I am trying to bridge the gap between the extensions supported by the C
> and C++ front-ends. When it comes to vector extensions, C++ supports
> vectors in comparisons and within conditional expressions whereas the C
On Mon, Oct 10, 2022 at 8:06 PM Arsen Arsenović via Gcc-patches
wrote:
>
> Evening,
>
> Ping on this patch, it should fix some configuration issues we get on
> ELF targets (especially in libstdc++).
>
> https://gcc.gnu.org/pipermail/gcc-patches/2022-October/602751.html
OK.
Thanks,
Richard.
> Th
On Mon, Oct 10, 2022 at 5:10 PM Jonathan Wakely wrote:
>
> On Mon, 10 Oct 2022 at 12:17, Jonathan Wakely wrote:
> >
> > On Mon, 10 Oct 2022 at 07:18, Richard Biener
> > wrote:
> > >
> > > On Fri, Oct 7, 2022 at 5:55 PM Jonathan Wakely via Gcc-patches
> > > wrote:
> > > >
> > > > This needs a l
On Mon, Oct 10, 2022 at 4:23 PM Tom de Vries wrote:
>
> On 10/10/22 16:19, Thomas Schwinge wrote:
> > With that, OK to push?
>
> FWIW, nvptx change looks in the obvious category to me.
Can you rename the functions as default_asm_out_* and instead of
reviving dbxout.cc
put them into targhooks.cc?
From: Ju-Zhe Zhong
gcc/ChangeLog:
* config/riscv/riscv-vector-builtins.h (DEF_RVV_TYPE): Clang-format it.
---
gcc/config/riscv/riscv-vector-builtins.h | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/gcc/config/riscv/riscv-vector-builtins.h
b/gcc/config/riscv/risc
From: Ju-Zhe Zhong
gcc/ChangeLog:
* config/riscv/riscv-vector-builtins.cc: Change include files same as
ARM SVE.
* config/riscv/t-riscv: Refine makefile.
---
gcc/config/riscv/riscv-vector-builtins.cc | 9 +++--
gcc/config/riscv/t-riscv | 14 --
From: Ju-Zhe Zhong
gcc/ChangeLog:
* config/riscv/riscv-vector-builtins.h: Remove redundant macro.
---
gcc/config/riscv/riscv-vector-builtins.h | 3 ---
1 file changed, 3 deletions(-)
diff --git a/gcc/config/riscv/riscv-vector-builtins.h
b/gcc/config/riscv/riscv-vector-builtins.h
inde
From: Ju-Zhe Zhong
gcc/ChangeLog:
* config/riscv/riscv-vector-builtins.cc (add_vector_type_attribute):
Clang-format function.
---
gcc/config/riscv/riscv-vector-builtins.cc | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/gcc/config/riscv/riscv-vector-builtins.cc
From: Ju-Zhe Zhong
gcc/ChangeLog:
* config/riscv/riscv-vector-builtins.cc (GTY): Redefine vector types.
(build_const_pointer): New function.
(register_builtin_type): Ditto.
(DEF_RVV_TYPE): Simplify macro.
(register_vector_type): Refine implementation.
From: Ju-Zhe Zhong
gcc/ChangeLog:
* config/riscv/riscv-vector-builtins.cc (rvv_switcher::rvv_switcher):
Move down like ARM SVE.
(rvv_switcher::~rvv_switcher): Move down like ARM SVE.
(mangle_builtin_type): Move down to make it together with other global
function.
When turning a jump to a return into a return, we need to clear
EDGE_CROSSING of the fallthru edge to prevent a checking failure.
I considered not applying the transformation when the edge has
EDGE_CROSSING set, but it still seems like we ought to eliminate the
unnecessary jump in that case.
On 10/10/22 18:36, Eugene Rozenfeld via Gcc-patches wrote:
The bug was introduced in f30e9fd33e56a5a721346ea6140722e1b193db42.
A variable (cur_locus_e) was incorrectly declared inside a loop.
I also moved two other declarations (last and locus) down to make
the code more clear.
Tested on x86_6
On 10/10/22 20:36, Eugene Rozenfeld wrote:
The bug was introduced in f30e9fd33e56a5a721346ea6140722e1b193db42.
A variable (cur_locus_e) was incorrectly declared inside a loop.
I also moved two other declarations (last and locus) down to make
the code more clear.
Tested on x86_64-pc-linux-gnu.
Tested on x86_64-pc-linux-gnu, does this look OK for trunk? (The paper
also makes changes to views::take and views::drop, which will be
implemented separately.)
libstdc++-v3/ChangeLog:
* include/std/ranges (repeat_view): Define.
(repeat_view::_Iterator): Define.
(views::__
Committed, thanks :)
On Mon, Oct 10, 2022 at 9:58 PM wrote:
>
> From: Ju-Zhe Zhong
>
> gcc/ChangeLog:
>
> * config/riscv/riscv-vector-builtins.cc (struct vector_type_info):
> Move from config/riscv/riscv-vector-builtins.h.
> (DEF_RVV_TYPE): Change USER_NAME to NAME.
> (r
Committed, thanks :)
On Mon, Oct 10, 2022 at 9:44 PM wrote:
>
> From: Ju-Zhe Zhong
>
> When implementing built-in framework, I notice I missed
> vsetvl instruction type, so add it in a single patch
> preparing for the following patches.
>
> gcc/ChangeLog:
>
> * config/riscv/riscv.md: Add
On Mon, Oct 10, 2022 at 5:37 PM Eugene Rozenfeld
wrote:
>
> The bug was introduced in f30e9fd33e56a5a721346ea6140722e1b193db42.
> A variable (cur_locus_e) was incorrectly declared inside a loop.
> I also moved two other declarations (last and locus) down to make
> the code more clear.
>
> Tested o
I sent a patch that fixes a bug introduced by this patch:
https://gcc.gnu.org/pipermail/gcc-patches/2022-October/603203.html
What you are seeing could have been caused by the same bug since it involves an
uninitialized variable.
Eugene
On Oct 10, 2022, at 5:54 PM, David Edelsohn wrote:
Th
This patch causes a bootstrap comparison failure on AIX. It apparently
does not cause a failure on PPC64BE Linux with the same ABI, so I suspect
that the failure may be related to the way that function aliases are
implemented on AIX, which doesn't have ELF symbol alias semantics.
"This change wil
The bug was introduced in f30e9fd33e56a5a721346ea6140722e1b193db42.
A variable (cur_locus_e) was incorrectly declared inside a loop.
I also moved two other declarations (last and locus) down to make
the code more clear.
Tested on x86_64-pc-linux-gnu.
gcc/ChangeLog:
PR debug/107193
On Mon, 10 Oct 2022, Paul Iannetta via Gcc-patches wrote:
> I have a patch to bring this feature to the C front-end as well, and
> would like to hear your opinion on it, especially since it may affect
> the feature-set of the objc front-end as well.
> Currently, this is only a tentative patch and
This Go frontend patch treats S("") as a string constant. The
compiler neglected to notice that a conversion from a string constant
to a string type was a valid string constant.
I didn't add a test case because this only caused a compiler failure
when compiling without optimization, which is not
This patch to the Go frontend delays building the struct type for a
go/defer thunk until it is needed. We were building it in the
determine_types pass. Now, we delay until the
simplify_thunk_statements pass. That ensures that we are consistent
in determining whether an argument is constant.
Wit
On Mon, Oct 10, 2022 at 05:09:29PM -0400, Jason Merrill wrote:
> On 10/10/22 04:54, Jakub Jelinek via Gcc-patches wrote:
> > My earlier patches gimplify the simplest non-side-effects assumptions
> > into if (cond) ; else __builtin_unreachable (); and throw the rest
> > on the floor.
> > The followi
On 10/10/22 04:54, Jakub Jelinek via Gcc-patches wrote:
Hi!
My earlier patches gimplify the simplest non-side-effects assumptions
into if (cond) ; else __builtin_unreachable (); and throw the rest
on the floor.
The following patch attempts to do something with the rest too.
For -O0, it actually
On 10/4/22 11:12, Ben Boeckel wrote:
This patch implements support for [P1689R5][] to communicate to a build
system the C++20 module dependencies to build systems so that they may
build `.gcm` files in the proper order.
Thanks!
Support is communicated through the following three new flags:
-
On 10/4/22 13:36, Patrick Palka wrote:
Here when lazily loading the binding for f at parse time from the
template g, processing_template_decl is set and thus the call to
note_vague_linkage_fn from module_state::read_cluster has no effect,
and we never push f onto deferred_fns and end up never emi
On Mon, 10 Oct 2022 at 15:05, Jonathan Wakely wrote:
>
> On Mon, 10 Oct 2022 at 14:50, Tim Song via Libstdc++
> wrote:
> >
> > On Mon, Oct 10, 2022 at 8:09 AM Patrick Palka via Libstdc++
> > wrote:
> > >
> > > On Mon, 10 Oct 2022, Jonathan Wakely via Libstdc++ wrote:
> > >
> > > > Tested powerpc6
On 10/4/22 11:11, Ben Boeckel wrote:
This patch adds initial support for ISO C++'s [P1689R5][], a format for
describing C++ module requirements and provisions based on the source
code. This is required because compiling C++ with modules is not
embarrassingly parallel and need to be ordered to ens
On 9/28/22 17:26, Marek Polacek wrote:
This patch removes the two-stage overload resolution when performing
implicit move, whereby the compiler does two separate overload resolutions:
one treating the operand as an rvalue, and then (if that resolution fails)
another one treating the operand as an
On Mon, 10 Oct 2022 at 19:06, Olivier Hainque via Libstdc++
wrote:
>
> Sorry, I forgot to cc libstdc++ on
>
> https://gcc.gnu.org/pipermail/gcc-patches/2022-October/603182.html
>
> which includes a regen of libstdc++-v3/configure after an update
> libtool.m4.
OK, thanks for the heads up.
On 10/10/22 15:18, Marek Polacek wrote:
On Mon, Oct 10, 2022 at 10:49:34AM -0400, Jason Merrill wrote:
On 10/7/22 18:16, Marek Polacek wrote:
On Fri, Oct 07, 2022 at 05:56:18PM -0400, Jason Merrill wrote:
On 10/7/22 17:08, Marek Polacek wrote:
On Fri, Oct 07, 2022 at 12:17:34PM -0400, Jason M
On 10/9/22 12:12, Paul Iannetta wrote:
Hi,
On Thu, Oct 06, 2022 at 01:34:40PM -0400, Jason Merrill wrote:
[snip]
Hmm? We mangle __restrict:
void f(int *__restrict *p) { } // _Z1fPrPi
Indeed, I have overlooked that point. Thank you for pointing it out.
but cv-qualifiers (including restr
Ping.
On Wed, Sep 28, 2022 at 05:26:34PM -0400, Marek Polacek via Gcc-patches wrote:
> This patch removes the two-stage overload resolution when performing
> implicit move, whereby the compiler does two separate overload resolutions:
> one treating the operand as an rvalue, and then (if that resol
On Mon, Oct 10, 2022 at 10:49:34AM -0400, Jason Merrill wrote:
> On 10/7/22 18:16, Marek Polacek wrote:
> > On Fri, Oct 07, 2022 at 05:56:18PM -0400, Jason Merrill wrote:
> > > On 10/7/22 17:08, Marek Polacek wrote:
> > > > On Fri, Oct 07, 2022 at 12:17:34PM -0400, Jason Merrill wrote:
> > > > > On
Le 23/09/2022 à 09:54, Mikael Morin a écrit :
Le 22/09/2022 à 22:42, Harald Anlauf via Fortran a écrit :
This LGTM. It also fixes a regression introduced with r9-3030 :-)
If you think that this set (1-3) is backportable, feel free to do so.
Yes, 2 and 3 are worth backporting, I will see how d
[Andrew, you OK with this? I can't tell whether the trailer() call was
actually needed.]
logical_combine is calling tracer.trailer() one too many times causing
the second trailer() call to subtract a 0 indent by 2, yielding an
indent of SOMETHING_REALLY_BIG :). You'd be surprised how many tools
Evening,
Ping on this patch, it should fix some configuration issues we get on
ELF targets (especially in libstdc++).
https://gcc.gnu.org/pipermail/gcc-patches/2022-October/602751.html
Thanks,
--
Arsen Arsenović
signature.asc
Description: This is a digitally signed message part.
Sorry, I forgot to cc libstdc++ on
https://gcc.gnu.org/pipermail/gcc-patches/2022-October/603182.html
which includes a regen of libstdc++-v3/configure after an update
libtool.m4.
Not committed yet.
With Kind Regards,
Olivier
> On 10 Oct 2022, at 19:05, Olivier Hainque wrote:
>
> Hello,
On Tue, Sep 27, 2022 at 3:04 AM Lulu Cheng wrote:
>
> v1 - > v2:
>
> 1. When the macro __loongarch_lp64 is defined, the VTV_PAGE_SIZE is set to
> 64K.
> 2. In the vtv_malloc.cc file __vtv_malloc_init function, it does not check
>whether VTV_PAGE_SIZE is equal to the system page size, if the m
Hello,
This change introduces configury infrastructure allowing the
production of shared libraries for VxWorks, amenable to use with
non-static rtps (linked with "-non-static").
The ability to produce PIC code is not a given on all VxWorks
configurations, so activating this has to be explicitly r
在 2022-10-04 20:44, LIU Hao 写道:
Attached are revised patches. These are exported from trunk.
Revised further. The patch for libgfortran has been committed to trunk today, so I include only the
other two.
* In the second patch, a space character has been inserted after
`(int)` for clea
On Thu, Jul 28, 2022 at 5:40 AM Richard Sandiford via Gcc-patches
wrote:
>
> Seems this thread has become a bit heated, so I'll try to proceed
> with caution :-)
>
> In the below, I'll use "X-mode const_int" to mean "a const_int that
> is known from context to represent an X-mode value". Of cours
Hi Paul,
> On 10 Oct 2022, at 16:20, Paul Iannetta wrote:
> On Mon, Oct 10, 2022 at 03:37:24PM +0100, Iain Sandoe wrote:
>> Hi Paul,
>>
>> Not a review of the patch - but a couple of observations.
>>
>>> On 10 Oct 2022, at 15:11, Paul Iannetta via Gcc-patches
>>> wrote:
>>
>>> I am trying t
This patch set contains the .h, .cc and .flex files found in
gcc/m2. The files are tightly coupled with the gimple interface
(see 04-gimple-interface) and built using the rules found in
(01-03-make).
--8<--8<--8<--8<--8<--8<
diff -ruw /dev/nul
This patch set contains the bootstrap linking tool as well as python3
scripts to automatically generate texi libraries section of the gm2
documentation. In the fullness of time this will be changed to emit
sphinx.
--8<--8<--8<--8<--8<--8<
diff
This patchset contains the gimple interface.
--8<--8<--8<--8<--8<--8<
diff -ruw /dev/null gcc-git-devel-modula2/gcc/m2/gm2-gcc/m2assert.cc
--- /dev/null 2022-08-24 16:22:16.88870 +0100
+++ gcc-git-devel-modula2/gcc/m2/gm2-gcc/m2assert.cc
This patch set consists of the makefiles, autoconf sources necessary
to build the various libgm2/libm2pim libraries. The c/c++/h files
are included in the patch set. The modula-2 sources are found in
gcc/m2/ as they are used by the compiler.
--8<--8<--8<--8<-
This patch set consists of the makefiles, autoconf sources necessary
to build the various libgm2/libm2iso libraries. The c/c++/h files
are also included in the patch set. The modula-2 sources are found
in gcc/m2.
--8<--8<--8<--8<--8<--8<
diff
Here are the dejagnu expect library scripts for the gm2
testsuite.
--8<--8<--8<--8<--8<--8<
diff -ruw /dev/null gcc-git-devel-modula2/gcc/testsuite/lib/gm2.exp
--- /dev/null 2022-08-24 16:22:16.88870 +0100
+++ gcc-git-devel-modula2/gcc/te
This patchset contains the gimple interface.
--8<--8<--8<--8<--8<--8<
diff -ruw /dev/null gcc-git-devel-modula2/gcc/m2/gm2-gcc/m2linemap.cc
--- /dev/null 2022-08-24 16:22:16.88870 +0100
+++ gcc-git-devel-modula2/gcc/m2/gm2-gcc/m2linemap.c
This patchset contains the modula2 plugin which detects some runtime
errors at compiletime.
--8<--8<--8<--8<--8<--8<
diff -ruw /dev/null gcc-git-devel-modula2/gcc/m2/plugin/m2rte.cc
--- /dev/null 2022-08-24 16:22:16.88870 +0100
+++ gcc-gi
This patchset contains the gimple interface.
--8<--8<--8<--8<--8<--8<
diff -ruw /dev/null gcc-git-devel-modula2/gcc/m2/gm2-gcc/init.cc
--- /dev/null 2022-08-24 16:22:16.88870 +0100
+++ gcc-git-devel-modula2/gcc/m2/gm2-gcc/init.cc2
This patch set contains the non machine generated changes found in /
for example the language die and documentation changes. It also
contains the changes to the top level build Makefile infastructure
and the install.texi sourcebuild.texi documentation.
--8<--8<--8<---
This patch set consists of the libgm2 makefile, autoconf sources
necessary to build the libm2pim, libm2iso, libm2min, libm2cor
and libm2log.
--8<--8<--8<--8<--8<--8<
diff -ruw /dev/null gcc-git-devel-modula2/libgm2/ChangeLog
--- /dev/null 202
The makefile fragment for modula2 which builds the gm2 driver and cc1gm2.
--8<--8<--8<--8<--8<--8<
diff -ruw /dev/null gcc-git-devel-modula2/gcc/m2/Make-lang.in
--- /dev/null 2022-08-24 16:22:16.88870 +0100
+++ gcc-git-devel-modula2/gcc/m
This patch set consists of the makefiles, autoconf and a few C sources
to build the libgm2/libm2min libraries.
--8<--8<--8<--8<--8<--8<
diff -ruw /dev/null gcc-git-devel-modula2/libgm2/libm2min/Makefile.am
--- /dev/null 2022-08-24 16:22:16.88
This patchset contains the c++, h and option related files necessary
to build the driver program gm2. The patch also consists of the
autoconf/configure related build infastructure sources found in
gcc/m2. The reviewer might need to look at the 01-02-make patchset.
The gm2 driver is heavily bas
This patch set consists of the makefiles, autoconf sources necessary
to build the various libgm2 libraries. The c/c++/h files are included
in the patch set. The modula-2 sources are found in gcc/m2.
--8<--8<--8<--8<--8<--8<
diff -ruw /dev/nul
Here are the latest modula-2 front end patches for review.
The status of the patches and their contents are also contained at:
https://splendidisolation.ddns.net/public/modula2/patchsummary.html
where they are also broken down into topic groups.
In summary the high level changes from the la
ping^2 ?
On 10/5/22 16:55, Christophe Lyon via Gcc-patches wrote:
ping?
On 9/12/22 10:13, Christophe Lyon via Gcc-patches wrote:
Hi!
On 9/9/22 11:33, Christophe Lyon wrote:
This is a backport from trunk to gcc-12.
Several MVE builtins incorrectly use the same predicate/constraint
pair for
Hi Ian,
Observations are also very welcomed, thank you!
On Mon, Oct 10, 2022 at 03:37:24PM +0100, Iain Sandoe wrote:
> Hi Paul,
>
> Not a review of the patch - but a couple of observations.
>
> > On 10 Oct 2022, at 15:11, Paul Iannetta via Gcc-patches
> > wrote:
>
> > I am trying to bridge t
On Mon, 10 Oct 2022 at 12:17, Jonathan Wakely wrote:
>
> On Mon, 10 Oct 2022 at 07:18, Richard Biener
> wrote:
> >
> > On Fri, Oct 7, 2022 at 5:55 PM Jonathan Wakely via Gcc-patches
> > wrote:
> > >
> > > This needs a little more documentation (see the TODO in the manual),
> > > rather than jus
On 10/7/22 18:16, Marek Polacek wrote:
On Fri, Oct 07, 2022 at 05:56:18PM -0400, Jason Merrill wrote:
On 10/7/22 17:08, Marek Polacek wrote:
On Fri, Oct 07, 2022 at 12:17:34PM -0400, Jason Merrill wrote:
On 10/6/22 22:12, Marek Polacek wrote:
On Thu, Oct 06, 2022 at 05:42:41PM -0400, Jason Me
Hi Paul,
Not a review of the patch - but a couple of observations.
> On 10 Oct 2022, at 15:11, Paul Iannetta via Gcc-patches
> wrote:
> I am trying to bridge the gap between the extensions supported by the C
> and C++ front-ends. When it comes to vector extensions, C++ supports
> vectors in c
On 10/10/22 16:19, Thomas Schwinge wrote:
With that, OK to push?
FWIW, nvptx change looks in the obvious category to me.
Thanks,
- Tom
Hi!
On 2022-09-01T12:05:23+0200, Martin Liška wrote:
> Patch can bootstrap on x86_64-linux-gnu and survives regression tests.
>
> I've also built all cross compilers.
First: thanks for that: clean up plus "built all cross compilers"!
But yet, I've now tracked down an issue related to these chan
Hi,
I am trying to bridge the gap between the extensions supported by the C
and C++ front-ends. When it comes to vector extensions, C++ supports
vectors in comparisons and within conditional expressions whereas the C
front-end does not.
I have a patch to bring this feature to the C front-end as
RVV also doesn't have a two-input permutation instructions (unlike ARM SVE has
tbl instructions) and
RVV needs about 4 instructions to handle this permutation, it still improve
performance a lot.
I think backend should handle this. Because this first-order recurrence loop
vectorizer always gene
On Mon, 10 Oct 2022 at 14:50, Tim Song via Libstdc++
wrote:
>
> On Mon, Oct 10, 2022 at 8:09 AM Patrick Palka via Libstdc++
> wrote:
> >
> > On Mon, 10 Oct 2022, Jonathan Wakely via Libstdc++ wrote:
> >
> > > Tested powerpc64le-linux. Pushed to trunk.
> > >
> > > -- >8 --
> > >
> > > Currently we
Ignore this patch plz. It's not finished.
The correct && full patch is this:
https://gcc.gnu.org/pipermail/gcc-patches/2022-October/603148.html
Thanks.
juzhe.zh...@rivai.ai
From: juzhe.zhong
Date: 2022-10-10 21:49
To: gcc-patches
CC: kito.cheng; Ju-Zhe Zhong
Subject: [PATCH] RISC-V: move stru
On Mon, Oct 10, 2022 at 10:15:58AM +0800, Kewen.Lin wrote:
> on 2022/10/4 05:15, Segher Boessenkool wrote:
> > Right. If If mpowerpc64 is enabled while OS_MISSING_POWERPC64, warn for
> > that;
>
> Currently if option powerpc64 is enabled explicitly while
> OS_MISSING_POWERPC64,
> there is no wa
On 10/10/2022 12:03, Richard Biener wrote:
The following picks up the prototype by Ju-Zhe Zhong for vectorizing
first order recurrences. That solves two TSVC missed optimization PRs.
There's a new scalar cycle def kind, vect_first_order_recurrence
and it's handling of the backedge value vectori
From: Ju-Zhe Zhong
gcc/ChangeLog:
* config/riscv/riscv-vector-builtins.cc (struct vector_type_info): Move
from config/riscv/riscv-vector-builtins.h.
(DEF_RVV_TYPE): Change USER_NAME to NAME.
(register_vector_type): Change user_name to name.
* config/riscv/riscv-v
On Mon, Oct 10, 2022 at 8:09 AM Patrick Palka via Libstdc++
wrote:
>
> On Mon, 10 Oct 2022, Jonathan Wakely via Libstdc++ wrote:
>
> > Tested powerpc64le-linux. Pushed to trunk.
> >
> > -- >8 --
> >
> > Currently we only reject std::make_signed_t but not cv bool.
> > Similarly for std::make_unsign
From: Ju-Zhe Zhong
gcc/ChangeLog:
* config/riscv/riscv-vector-builtins.cc (struct vector_type_info): Move
from riscv-vector-builtins.h.
* config/riscv/riscv-vector-builtins.h (struct vector_type_info): Move
to riscv-vector-builtins.cc.
---
gcc/config/riscv/riscv-vector-builti
From: Ju-Zhe Zhong
When implementing built-in framework, I notice I missed
vsetvl instruction type, so add it in a single patch
preparing for the following patches.
gcc/ChangeLog:
* config/riscv/riscv.md: Add vsetvl instruction type.
---
gcc/config/riscv/riscv.md | 3 ++-
1 file chang
LGTM.
juzhe.zh...@rivai.ai
From: Kito Cheng
Date: 2022-10-10 21:14
To: gcc-patches; kito.cheng; christoph.muellner; juzhe.zhong
CC: Kito Cheng
Subject: [committed] RISC-V: Add riscv_vector.h wrapper in testsuite to prevent
pull in stdint.h from C library
For RISC-V linux/glibc toolchain will
LGTM.
juzhe.zh...@rivai.ai
From: Kito Cheng
Date: 2022-10-10 21:14
To: gcc-patches; kito.cheng; christoph.muellner; juzhe.zhong
CC: Kito Cheng
Subject: [committed] RISC-V: Adjust testcase for rvv/base/user-1.c
The -march option check isn't precise enough, -march=rv*v* also mach any
zve extensi
Jeff Law via Gcc-patches writes:
> On 9/27/22 09:12, Andrea Corallo via Gcc-patches wrote:
>> Hi all
>>
>> this is to address PR 99723.
>>
>> In the PR GCC crashes as the initialization of common trees is not
>> performed as no compilation is happening, this is because we raise an
>> error earlie
For RISC-V linux/glibc toolchain will got header file not found when including
stdint.h if multilib is not enabled, it because some header file will
try to include gnu/stubs-.h from the system, however it only
generated when multilib enabled.
In order to prevent that, we introduce a wrapper for ri
The -march option check isn't precise enough, -march=rv*v* also mach any
zve extensions.
gcc/testsuite/ChangeLog:
* gcc.target/riscv/rvv/base/user-1.c: Add dg-options and drop
dg-skip-if.
Reported-by: Christoph Müllner
Tested-by: Christoph Müllner
Reviewed-by: Ju-Zhe Zhong
---
gcc/ChangeLog:
* config/riscv/riscv-c.cc: Add newline to the end of file.
gcc/testsuite/ChangeLog:
* gcc.target/riscv/rvv/base/pragma-1.c: Add newline to the end of file.
* gcc.target/riscv/rvv/base/pragma-2.c: Ditto.
* gcc.target/riscv/rvv/base/pragma-3.c: Ditto.
On Mon, 10 Oct 2022, Jonathan Wakely via Libstdc++ wrote:
> Tested powerpc64le-linux. Pushed to trunk.
>
> -- >8 --
>
> Currently we only reject std::make_signed_t but not cv bool.
> Similarly for std::make_unsigned_t.
>
> As well as making those ill-formed, this adds a requires-clause to the
>
int_range<1> is a legacy range (think anti ranges, legacy VRP, etc).
There is a penalty for converting anything built with <1> to
non-legacy. Since most of the uses of these functions are now ranger,
we can save a miniscule amount of time by converting them to
non-legacy.
gcc/ChangeLog:
It is useful to know if there's the possiblity of a NAN with a given
sign. This is to complement maybe_isnan(void) which returns TRUE for a
NAN of any sign.
A follow-up patch implementing ABS will make use of this.
gcc/ChangeLog:
* value-range.h (frange::maybe_isnan): New.
---
gcc/valu
gcc/ChangeLog:
* range-op-float.cc (foperator_unordered::op1_range): Set NAN when
operands are equal and result is TRUE.
---
gcc/range-op-float.cc | 10 +++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/gcc/range-op-float.cc b/gcc/range-op-float.cc
index 685
gcc/ChangeLog:
* range-op-float.cc (foperator_not_equal::op1_range): Set NAN on
TRUE side for x != x.
---
gcc/range-op-float.cc | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/gcc/range-op-float.cc b/gcc/range-op-float.cc
index 91833d3f855..5ffe38da53a 1
gcc/ChangeLog:
* range-op-float.cc (class foperator_identity): Make members public.
(class foperator_equal): Same.
(class foperator_not_equal): Same.
(class foperator_lt): Same.
(class foperator_le): Same.
(class foperator_gt): Same.
(class f
Tested powerpc64le-linux. Pushed to trunk.
-- >8 --
Currently we only reject std::make_signed_t but not cv bool.
Similarly for std::make_unsigned_t.
As well as making those ill-formed, this adds a requires-clause to the
make_signed and make_unsigned primary templates. This makes
non-integral, no
On Mon, 10 Oct 2022 at 07:18, Richard Biener wrote:
>
> On Fri, Oct 7, 2022 at 5:55 PM Jonathan Wakely via Gcc-patches
> wrote:
> >
> > This needs a little more documentation (see the TODO in the manual),
> > rather than just the comments in the source. This isn't final, but I
> > think it's the
Thank you so much. I will apply this patch and test it in downstream RVV GCC
（12.2.0)
juzhe.zh...@rivai.ai
From: Richard Biener
Date: 2022-10-10 19:03
To: gcc-patches
CC: richard.sandiford; ams; juzhe.zhong
Subject: [PATCH][RFT] Vectorization of first-order recurrences
The following picks up t
The following picks up the prototype by Ju-Zhe Zhong for vectorizing
first order recurrences. That solves two TSVC missed optimization PRs.
There's a new scalar cycle def kind, vect_first_order_recurrence
and it's handling of the backedge value vectorization is complicated
by the fact that the ve
On Fri, 30 Sept 2022 at 21:38, Richard Sandiford
wrote:
>
> Richard Sandiford via Gcc-patches writes:
> > Prathamesh Kulkarni writes:
> >> Sorry to ask a silly question but in which case shall we select 2nd vector
> >> ?
> >> For num_poly_int_coeffs == 2,
> >> a1 /trunc n1 == (a1 + 0x) / (n1.co
On Sun, Oct 09, 2022 at 02:51:37PM -0700, Julian Brown wrote:
> This patch adds support for non-constant component offsets in "map"
> clauses for OpenMP (and the equivalants for OpenACC), which are not able
> to be sorted into order at compile time. Normally struct accesses in
> such clauses are g
Hi!
On Fri, Oct 07, 2022 at 02:26:56PM +0200, Richard Biener via Gcc-patches wrote:
> * gcc.dg/autopar/pr107153.c: New testcase.
The test uses -floop-parallelize-all which emits a sorry when graphite
isn't configured in.
Tested on x86_64-linux and i686-linux, committed to trunk as obvious.
I have committed this patch, as the __builtin_signbit range-op entry
is correct. I'd still like clarification on the folding).
Aldy
On Thu, Oct 6, 2022 at 12:51 PM Aldy Hernandez wrote:
>
> This is the op1_range range-op entry for __builtin_signbit. It allows
> us to wind back through a call t
Hi!
My earlier patches gimplify the simplest non-side-effects assumptions
into if (cond) ; else __builtin_unreachable (); and throw the rest
on the floor.
The following patch attempts to do something with the rest too.
For -O0, it actually throws even the simplest assumptions on the floor,
we don'
On Fri, Jul 29, 2022 at 8:36 AM Alexandre Oliva wrote:
>
> On Jul 29, 2022, Alexandre Oliva wrote:
>
> > This patch adds the strub attribute for function and variable types,
> > command-line options, passes and adjustments to implement it,
> > documentation, and tests.
>
> The entire patch, and t
1 - 100 of 109 matches
Mail list logo
