Hi Mike,
on 2022/12/7 14:44, Michael Meissner wrote:
> On Tue, Dec 06, 2022 at 05:36:54PM +0800, Kewen.Lin wrote:
>> Hi Mike,
>>
>> Thanks for fixing this!
>>
>> Could you help to elaborate why we need to disable it during libgcc building?
>
> When you are building libgcc, you are building the __
On 07.12.22 08:10, Thomas Schwinge wrote:
Hi!
On 2022-12-07T07:04:10+0100, Sebastian Huber
wrote:
On 06.12.22 22:06, Thomas Schwinge wrote:
I suppose I just fail to see some detail here, but:
On 2022-11-21T08:25:25+0100, Sebastian
Huber wrote:
gcc/ChangeLog:
* gcc.cc (SUBTARG
Hi!
On 2022-12-07T07:04:10+0100, Sebastian Huber
wrote:
> On 06.12.22 22:06, Thomas Schwinge wrote:
> I suppose I just fail to see some detail here, but:
>
>> On 2022-11-21T08:25:25+0100, Sebastian
>> Huber wrote:
>>> gcc/ChangeLog:
>>>
>>>* gcc.cc (SUBTARGET_CC1_SPEC): Define if not d
On Wed, Dec 7, 2022 at 7:36 AM Hongyu Wang wrote:
>
> For Alderlake there is similar issue like PR 81616, enable
> avoid_fma256_chain will also benefit on Intel latest platforms
> Alderlake and Sapphire Rapids.
>
> Bootstrapped/regtested on x86_64-pc-linux-gnu{-m32,}.
>
> Ok for master?
>
> gcc/Ch
On Tue, Dec 06, 2022 at 05:36:54PM +0800, Kewen.Lin wrote:
> Hi Mike,
>
> Thanks for fixing this!
>
> Could you help to elaborate why we need to disable it during libgcc building?
When you are building libgcc, you are building the __mulkc3, __divkc3
functions. The mapping in the compiler interf
For Alderlake there is similar issue like PR 81616, enable
avoid_fma256_chain will also benefit on Intel latest platforms
Alderlake and Sapphire Rapids.
Bootstrapped/regtested on x86_64-pc-linux-gnu{-m32,}.
Ok for master?
gcc/ChangeLog:
* config/i386/x86-tune.def (X86_TUNE_AVOID_256FMA_
On 06.12.22 22:06, Thomas Schwinge wrote:
Hi!
I suppose I just fail to see some detail here, but:
On 2022-11-21T08:25:25+0100, Sebastian
Huber wrote:
gcc/ChangeLog:
* gcc.cc (SUBTARGET_CC1_SPEC): Define if not defined.
(cc1_spec): Append SUBTARGET_CC1_SPEC.
---
v2: Append SUBT
on 2022/12/7 13:24, HAO CHEN GUI wrote:
> Hi Kewen,
> Thanks so much for your review comments. I will fix them.
>
> 在 2022/12/7 11:06, Kewen.Lin 写道:
>> Does this issue which relies on the fix for generic part make bootstrapping
>> fail?
>> If no, how many failures it can cause? I'm thinking if
Hi Kewen,
Thanks so much for your review comments. I will fix them.
在 2022/12/7 11:06, Kewen.Lin 写道:
> Does this issue which relies on the fix for generic part make bootstrapping
> fail?
> If no, how many failures it can cause? I'm thinking if we can commit this
> firstly,
> then in the commi
Hi,
This patch adds a new conversion to convert a certain branch to
conditional ternary set in ifcvt.
The branch commonly has following insns.
cond_jump ? pc : label
setcc
(neg/subreg)
label: set a constant
cond_jump and setcc use the same CC reg and neg/subreg is optional.
The br
Hi Haochen,
on 2022/12/6 13:44, HAO CHEN GUI wrote:
> Hi,
> This patch enables "have_cbranchcc4" on rs6000 by defining
> a "cbranchcc4" expander. "have_cbrnachcc4" is a flag in ifcvt.cc
> to indicate if branch by CC bits is invalid or not. With this
> flag enabled, some branches can be optimized
Hi,
In the recent discussion on how to make some built-in type only valid for
some target features efficiently[1], Andrew mentioned this patch which he
made previously (Thanks!). I confirmed it can help rs6000 related issue,
and noticed PR99657 is still opened, so I think we still want this to
be
gcc/ChangeLog:
* doc/rtl.texi: Correct a clerical error in the document.
---
gcc/doc/rtl.texi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/gcc/doc/rtl.texi b/gcc/doc/rtl.texi
index 43c9ee8bffe..44858d12892 100644
--- a/gcc/doc/rtl.texi
+++ b/gcc/doc/rtl.texi
@@ -214
I initially ran into this while reviving autoprofiledbootstrap build.
I was able to create a simple reliable test for this bug and captured it in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108000
I also included the test case in the updated patch below.
Eugene
===
Thanks Richard for your review and for pointing out the issue with BTI.
The current patch removes the existing BTI instruction,
and then adds the BTI hint when expanding the patchable_area pseudo.
The attached patch passed bootstrap and regression test on arm64-linux.
Ok to commit to gcc trun
PR analyzer/107882 reports an ICE, due to trying to get a compound svalue
for this binding:
cluster for: a:
key: {bytes 0-3}
value: {UNKNOWN()}
key: {empty}
value: {UNKNOWN()}
key: {bytes 4-7}
value: {UNKNOWN()}
where there's an binding to the unknown value of z
On Wed, 30 Nov 2022 at 18:00, François Dumont wrote:
>
> On 30/11/22 14:07, Jonathan Wakely wrote:
> > On Wed, 30 Nov 2022 at 11:57, Jonathan Wakely wrote:
> >>
> >>
> >> On Wed, 30 Nov 2022 at 11:54, Jonathan Wakely wrote:
> >>>
> >>>
> >>> On Wed, 30 Nov 2022 at 06:04, François Dumont via Libs
Tested x86_64-linux. Pushed to trunk.
-- >8 --
This test was recently modified to check that the library doesn't use
__unused anywhere, because that's a macro in newlib. But it's also a
macro in old versions of glibc, so the test now fails for those targets.
Disable that check for those targets a
Tested x86_64-linux. Pushed to trunk.
-- >8 --
libstdc++-v3/ChangeLog:
PR libstdc++/107871
* include/std/format (_Iter_sink::_M_overflow): Add cast to
size_t.
(_Iter_sink::_M_make_span): Use
typedef instead of decltype.
* testsuite/std/format/funct
I've pushed this to trunk. Tested x86_64-linux.
On Mon, 21 Nov 2022 at 20:44, Jonathan Wakely via Libstdc++
wrote:
>
> While finishing the time zone support for C++20, I noticed that the
> chrono::hh_mm_ss type is surprisingly large: 40 bytes. That's because
> we use duration for each of the four
Tested x86_64-linux. Pushed to trunk.
-- >8 --
The PR shows a bogus warning where jump threading generates code for the
undefined case that the insertion point is a value-initialized iterator
but _M_finish and _M_end_of_storage are unequal (so at least one must be
non-null). Using __builtin_unrea
Tested x86_64-linux. Pushed to trunk.
-- >8 --
libstdc++-v3/ChangeLog:
* include/bits/std_mutex.h (mutex): Add nodiscard attribute to
try_lock member function.
* include/bits/unique_lock.h (unique_lock): Likewise for
try_lock, try_lock_until, try_lock_for member f
Tested x86_64-linux. Pushed to trunk.
-- >8 --
Fix digit grouping for integers formatted with "{:#Lx}" which were
including the "0x" prefix in the grouped digits. This resulted in output
like "0,xff,fff" instead of "0xff,fff".
Also change std:::basic_format_parse_context to not throw for an arg-
The 12/06/2022 11:58, Wilco Dijkstra wrote:
> > i don't think how[*RA_STATE] can ever be set to REG_SAVED_OFFSET,
> > this pseudo reg is not spilled to the stack, it is reset to 0 in
> > each frame and then toggled within a frame.
>
> It's is just a state, we can use any state we want since it is
Hi!
I suppose I just fail to see some detail here, but:
On 2022-11-21T08:25:25+0100, Sebastian Huber
wrote:
> gcc/ChangeLog:
>
> * gcc.cc (SUBTARGET_CC1_SPEC): Define if not defined.
> (cc1_spec): Append SUBTARGET_CC1_SPEC.
> ---
> v2: Append SUBTARGET_CC1_SPEC directly to cc1_spec
From: Björn Schäpers
This is actually needed so that libstdc++'s implementation
to be able to work on windows.
Tested on x86_64-linux and i686-w64-mingw32.
-- >8 --
* configure.ac: Add a check for windows.h.
* configure, config.h.in: Regenerate.
* fileline.c: Add windo
From: Björn Schäpers
Any underflow which might happen, will be countered by an overflow in
dwarf.c.
Tested on x86_64-linux and i686-w64-mingw32.
-- >8 --
Fixes https://github.com/ianlancetaylor/libbacktrace/issues/89 and
https://github.com/ianlancetaylor/libbacktrace/issues/82.
* peco
From: Björn Schäpers
Fixes https://github.com/ianlancetaylor/libbacktrace/issues/53, except
that libraries loaded after the backtrace_initialize are not handled.
But as far as I can see that's the same for elf.
Tested on x86_64-linux and i686-w64-mingw32.
-- >8 --
* pecoff.c (coff_add)
From: Björn Schäpers
It's the right thing to do, since the PC shouldn't go out of the
uintptr_t domain, and in backtrace_pcinfo the pc is uintptr_t.
This is a preparation for a following patch.
Tested on x86_64-linux and i686-w64-mingw32.
-- >8 --
* dwarf.c: changed variables holding p
Version 4 contains two missed feedback suggestions (namespace in
m2pp.cc) and use build_nonstandard_integer_type in
gm2-lang.cc:gm2_type_for_size.
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-interfac
On 12/5/22 19:35, Jakub Jelinek via Gcc-patches wrote:
Hi!
According to
https://gcc.gnu.org/pipermail/gcc-regression/2022-December/077258.html
Seen in the wild too - compiling one of the two weather forecasting
programs I use:
during GIMPLE pass: dom
/home/toon/scratch/hm_home/my_CY46h1/l
PR analyzer/106325 reports false postives from
-Wanalyzer-null-dereference on code like this:
__attribute__((nonnull))
void foo_a (Foo *p)
{
foo_b (p);
switch (p->type)
{
/* ... */
}
}
where foo_b (p) has a:
g_return_if_fail (p);
that expands to:
if (!p)
{
retu
Lightly tested with doxygen; with this patch it generates docs for the
analyzer internals (e.g. class hierarchies).
Pushed to trunk as r13-4519-gfa19bfbb0a1995.
contrib/ChangeLog:
* gcc.doxy (INPUT): Add gcc/analyzer subdirectory.
Signed-off-by: David Malcolm
---
contrib/gcc.doxy | 2 +
Successfully built on x86_64-pc-linux-gnu.
Pushed to trunk as r13-4518-g14b0d6c4bd973c.
gcc/ChangeLog:
* doc/analyzer.texi: Drop out-of-date ideas for other checkers.
Signed-off-by: David Malcolm
---
gcc/doc/analyzer.texi | 10 --
1 file changed, 10 deletions(-)
diff --git a/gc
Successfully bootstrapped & regrtested on x86_64-pc-linux-gnu.
Pushed to trunk as r13-4517-g861c917a972dc9.
gcc/ChangeLog:
* Makefile.in (ANALYZER_OBJS): Add analyzer/call-details.o,
analyzer/kf-analyzer.o, and kf-lang-cp.o.
gcc/analyzer/ChangeLog:
* analyzer.h (register_k
On Tue, 6 Dec 2022, Patrick Palka wrote:
> This patch fixes some issues with substitution into a C++20 template
> parameter object wrapper:
>
> * The first testcase demonstrates a situation where the same_type_p
> assert in relevant case of tsubst_copy doesn't hold, because (partial)
> substi
Hello,
I'm happy to give you a current report on the email participant database for
"DISTRIBUTECH International 2023".
Delegates are:
* Transmission grid owner / operator
* Distribution grid owner / operator
* Energy service provider
* Publicly owned
* Municipal
* IOU / Co
On 31/10/2022 15:36, Srinath Parvathaneni via Gcc-patches wrote:
Hi,
This patch adds the support for pacbti multlilib linking by making
"-mbranch-protection=none" as default in the command line for all M-profile
targets and uses "-mbranch-protection=none" for multilib matching. If any
valid v
This patch fixes some issues with substitution into a C++20 template
parameter object wrapper:
* The first testcase demonstrates a situation where the same_type_p
assert in relevant case of tsubst_copy doesn't hold, because (partial)
substitution of {int,} into the VIEW_CONVERT_EXPR wrapper yi
Richard Earnshaw writes:
> On 06/12/2022 15:46, Andrea Corallo wrote:
>> Hi Richard,
>> thanks for reviewing.
>> Just one clarification before I complete the respin of this patch.
>> Richard Earnshaw writes:
>> [...]
>>
>>> Also, I think (out of an abundance of caution) we really need a
>>> sch
On 06/12/2022 15:46, Andrea Corallo wrote:
Hi Richard,
thanks for reviewing.
Just one clarification before I complete the respin of this patch.
Richard Earnshaw writes:
[...]
Also, I think (out of an abundance of caution) we really need a
scheduling barrier placed before calls to gen_au
On Tue, 6 Dec 2022, Qing Zhao wrote:
> A. add the following to clarify the relationship between -Warray-bounds
> and the LEVEL of -fstrict-flex-array:
>
> By default, the trailing array of a structure will be treated as a
> flexible array member by '-Warray-bounds' or '-War
'-Wstrict-flex-arrays'
Warn about inproper usages of flexible array members according to
the LEVEL of the 'strict_flex_array (LEVEL)' attribute attached to
the trailing array field of a structure if it's available,
otherwise according to the LEVEL of the option
'-fstrict-fl
Sorry, Please ignore this email.
Qing
> On Dec 6, 2022, at 11:14 AM, Qing Zhao wrote:
>
> '-Wstrict-flex-arrays'
> Warn about inproper usages of flexible array members according to
> the LEVEL of the 'strict_flex_array (LEVEL)' attribute attached to
> the trailing array field of a s
'-Wstrict-flex-arrays'
Warn about inproper usages of flexible array members according to
the LEVEL of the 'strict_flex_array (LEVEL)' attribute attached to
the trailing array field of a structure if it's available,
otherwise according to the LEVEL of the option
'-fstrict-fl
A. add the following to clarify the relationship between -Warray-bounds
and the LEVEL of -fstrict-flex-array:
By default, the trailing array of a structure will be treated as a
flexible array member by '-Warray-bounds' or '-Warray-bounds=N' if
it is declared as either a
Hi, this is the 3rd version of the patch.
Per Richard's request, I split the patch into two seperate patches:
1. Update -Warray-bounds with -fstrict-flex-arrays.
2. Add a new warning option -Wstrict-flex-arrays.
I have bootstrapped and regression tested on both X86 and aarch64
without any issu
Tamar Christina via Gcc-patches writes:
> Hi All,
>
> The target has various zero and sign extension patterns. These however live
> in
> various locations around the MD file and almost all of them are split
> differently. Due to the various patterns we also ended up missing valid
> extensions.
Hi Richard,
thanks for reviewing.
Just one clarification before I complete the respin of this patch.
Richard Earnshaw writes:
[...]
> Also, I think (out of an abundance of caution) we really need a
> scheduling barrier placed before calls to gen_aut_nop() pattern is
> emitted, to ensure that
Prathamesh Kulkarni via Gcc-patches writes:
> On Fri, 4 Nov 2022 at 14:00, Prathamesh Kulkarni
> wrote:
>>
>> On Mon, 31 Oct 2022 at 15:27, Richard Sandiford
>> wrote:
>> >
>> > Prathamesh Kulkarni writes:
>> > > On Wed, 26 Oct 2022 at 21:07, Richard Sandiford
>> > > wrote:
>> > >>
>> > >> Sor
On Tue, Dec 06, 2022 at 08:56:09AM -0600, Segher Boessenkool wrote:
> > In the past, _Float128 was a C extended type,
> > but now it is a part of the C/C++ 2x standards.
>
> Only if you select a new enough -std=, it still is an extended type if
> not?
No, as an extension _Float{16,32,64,1
Hi!
On Tue, Nov 01, 2022 at 10:39:04PM -0400, Michael Meissner wrote:
> The basic issue is internally within GCC there are several types for 128-bit
> floating point. The types are:
>
> 1)The long double type (TFmode or possibly DFmode).
Please be very careful to call types types an
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 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
Here are the latest modula-2 front end patches. Since the posting in
https://gcc.gnu.org/pipermail/gcc-patches/2022-October/603161.html
I've rewritten the python3 documentation scripts (feedback from
patchset 16) and applied all the suggestions from the feedback in
patchset 15 (gm2-lang.cc).
Al
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
Hi Martin,
here is the revised patch having applied all previous recommendations:
https://gcc.gnu.org/pipermail/gcc-patches/2022-October/603436.html.
Is this ok now? Thanks for the improvement suggestions.
--8<--8<--8<--8<--8<--8<
diff -ruw /d
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 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 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<-
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 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 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
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 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 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
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 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
From: Yannick Moy
SPARK RM now allow the property No_Caching on volatile types, to
indicate that they should be considered volatile for compilation, but
not by GNATprove's analysis.
gcc/ada/
* contracts.adb (Add_Contract_Item): Allow No_Caching on types.
(Check_Type_Or_Object_Ex
From: Eric Botcazou
The problem is that the computation of early call regions skips freeze nodes
but scenarios involving procedures declared as actions of these freeze nodes
are taken into account. As a consequence if a subprogram body, typically of
an expression function, is placed just after a
From: Eric Botcazou
Like in Exp_Ch4, we do not want to give warnings in Sem_Warn on a membership
test with a mark for a subtype that is predicated.
gcc/ada/
* sem_warn.adb (Warn_On_Constant_Valid_Condition): Bail out for a
membership test with a mark for a subtype that is predic
From: Eric Botcazou
It's needed because, in GNAT, universal_integer does not cover all the
values of all the supported integer types.
gcc/ada/
* sem_res.adb (Resolve_Membership_Op): Adjust latest change.
Tested on x86_64-pc-linux-gnu, committed on master.
---
gcc/ada/sem_res.adb | 18
From: Eric Botcazou
This implements elision of the copy operation for extended return statements
in the case of nonlimited by-reference types (the copy operation is already
elided for limited types by the front-end and nonlimited non-by-reference
types by the code generator), which comprise contr
From: Javier Miranda
gcc/ada/
* exp_ch6.adb
(Build_Static_Check_Helper_Call): Perform implicit type conversion
to ensure matching types and avoid reporting spurious errors.
Tested on x86_64-pc-linux-gnu, committed on master.
---
gcc/ada/exp_ch6.adb | 7 ---
1 file
From: Eric Botcazou
When a membership test is applied to a nonstatic expression of a universal
type, for example an attribute whose type is universal_integer and whose
prefix is not static, the operation is performed using the tested type that
is determined by the choice list. In particular, a c
From: Liaiss Merzougue
This patch simplify the TO_C code to have a single branch for
raising exception. Furthermore, adding pragma annotate for codepeer
to ignore uninitialized value since this is caused because we have
input check before the initialization.
gcc/ada/
* libgnat/i-c.adb (
Tested x86_64-pc-linux-gnu, OK for trunk?
-- 8< --
The PR (which isn't resolved by this commit) pointed out to me that GCC
should build with -Wconditionally-supported to support bootstrapping with a
C++11 compiler that makes different choices.
PR c++/64867
gcc/ChangeLog:
* conf
On Tue, 6 Dec 2022, Iain Buclaw wrote:
> Now that the D front-end documentation has been generated and pushed to
> the site after r13-4421, this can be added to the main index page.
>
> This is a simple copy from other entries, so have gone ahead and
> committed it.
Cool, thank you. And sorry, I
Hi John,
On Tue, Dec 06, 2022 at 12:57:17PM +0100, John Paul Adrian Glaubitz wrote:
> On 12/6/22 12:40, Arthur Cohen wrote:
> > > Can't wait to see this becoming available in the distributions :D.
> > >
> > > I will make sure we get the frontend enabled in Debian as soon as
> > > possible.
> >
Hi,
Now that the D front-end documentation has been generated and pushed to
the site after r13-4421, this can be added to the main index page.
This is a simple copy from other entries, so have gone ahead and
committed it.
Regards,
Iain.
---
htdocs/onlinedocs/index.html | 6 ++
1 file chang
Hi!
On Thu, Nov 24, 2022 at 11:24:15AM +0100, Richard Biener wrote:
> On Thu, Nov 24, 2022 at 8:25 AM HAO CHEN GUI wrote:
> > 在 2022/11/24 4:06, Richard Biener 写道:
> > > Wouldn't we usually either add an optab or try to recog a canonical
> > > RTL form instead of adding a new target hook for thin
New plan-- this patch is entirely pointless! I have reverted it in a
local build and had no regressions.
As such, simply do not review or consider this patch. I am not not
planning on re-sending the patchset even though it adjusts the patch
numbers because it is such an arduous process given that
Hi,
> i don't think how[*RA_STATE] can ever be set to REG_SAVED_OFFSET,
> this pseudo reg is not spilled to the stack, it is reset to 0 in
> each frame and then toggled within a frame.
It's is just a state, we can use any state we want since it is a pseudo reg.
These registers are global and shar
On 12/6/22 12:40, Arthur Cohen wrote:
Can't wait to see this becoming available in the distributions :D.
I will make sure we get the frontend enabled in Debian as soon as possible.
Haha, I appreciate the enthusiasm :) Please note however that despite the
language
being in, the compiler is sti
Excerpts from Richard Biener via Gcc-patches's message of Dezember 6, 2022
12:03 pm:
> On Tue, Dec 6, 2022 at 11:11 AM wrote:
>>
>> This patchset contains the fixed version of our most recent patchset. We
>> have fixed most of the issues noted in the previous round of reviews, and are
>> keeping
On 12/6/22 12:09, John Paul Adrian Glaubitz wrote:
On 12/6/22 12:03, Richard Biener via Gcc-rust wrote:
On Tue, Dec 6, 2022 at 11:11 AM wrote:
This patchset contains the fixed version of our most recent patchset. We
have fixed most of the issues noted in the previous round of reviews,
and
Ping!!
From: Gcc-patches
on behalf of
Srinath Parvathaneni via Gcc-patches
Sent: 09 November 2022 14:32
To: gcc-patches@gcc.gnu.org
Cc: Richard Earnshaw ; Kyrylo Tkachov
Subject: [GCC][PATCH 13/15, v4] arm: Add support for dwarf debug directives and
pseudo h
Ping!!
From: Srinath Parvathaneni
Sent: 31 October 2022 12:38
To: gcc-patches@gcc.gnu.org
Cc: Richard Earnshaw ; Christophe Lyon
Subject: RE: [GCC][PATCH v2] arm: Add cde feature support for Cortex-M55 CPU.
Hi,
> -Original Message-
> From: Christophe Ly
Ping!!
From: Gcc-patches
on behalf of
Srinath Parvathaneni via Gcc-patches
Sent: 31 October 2022 15:36
To: gcc-patches@gcc.gnu.org
Cc: Richard Earnshaw
Subject: [GCC][PATCH v2] arm: Add pacbti related multilib support for
armv8.1-m.main.
Hi,
This patch adds
Hi Mike,
Thanks for fixing this, some comments are inlined below.
on 2022/11/2 10:42, Michael Meissner wrote:
> This patch fixes the issue that GCC cannot build when the default long double
> is IEEE 128-bit. It fails in building libgcc, specifically when it is trying
> to buld the __mulkc3 func
> > - COSTS_N_INSNS (5), /* cost of FADD and FSUB insns. */
> > - COSTS_N_INSNS (5), /* cost of FMUL instruction. */
> > + COSTS_N_INSNS (7), /* cost of FADD and FSUB insns. */
> > + COSTS_N_INSNS (7), /* cost of FMUL in
> Patches 1 and 2 don't seem to have reached the mailing list.
File size issues on the receiving server. I bzip3 compressed them, but
they were still too big.
> -Original Message-
> From: Andre Simoes Dias Vieira
> Sent: Tuesday, December 6, 2022 11:19 AM
> To: 'gcc-patches@gcc.gnu.org'
> Cc: Kyrylo Tkachov ; Richard Earnshaw
>
> Subject: [PATCH] arm: Fix MVE's vcmp vector-scalar patterns [PR107987]
>
> Hi,
>
> This patch surrounds the sc
Hi,
This patch surrounds the scalar operand of the MVE vcmp patterns with a
vec_duplicate to ensure both operands of the comparision operator have the same
(vector) mode.
Regression tested on arm-none-eabi. Is this OK for trunk? And a backport to GCC
12?
gcc/ChangeLog:
PR target/107987
Hi,
this patch adds tunes needed for zen4 microarchitecture. I added two new knobs.
TARGET_AVX512_SPLIT_REGS which is used to specify that internally 512 vectors
are split to 256 vectors. This affects vectorization costs and reassociation
width. It probably should also affect RTX costs however I
On 12/6/22 12:03, Richard Biener via Gcc-rust wrote:
On Tue, Dec 6, 2022 at 11:11 AM wrote:
This patchset contains the fixed version of our most recent patchset. We
have fixed most of the issues noted in the previous round of reviews, and are
keeping some for later as they would otherwise crea
Tamar Christina writes:
>> -Original Message-
>> From: Richard Sandiford
>> Sent: Tuesday, December 6, 2022 10:28 AM
>> To: Tamar Christina
>> Cc: gcc-patches@gcc.gnu.org; nd ; Richard Earnshaw
>> ; Marcus Shawcroft
>> ; Kyrylo Tkachov
>> Subject: Re: [PATCH 5/8]AArch64 aarch64: Make ex
On Tue, Dec 6, 2022 at 11:11 AM wrote:
>
> This patchset contains the fixed version of our most recent patchset. We
> have fixed most of the issues noted in the previous round of reviews, and are
> keeping some for later as they would otherwise create too many conflicts with
> our updated developm
> -Original Message-
> From: Richard Sandiford
> Sent: Tuesday, December 6, 2022 10:28 AM
> To: Tamar Christina
> Cc: gcc-patches@gcc.gnu.org; nd ; Richard Earnshaw
> ; Marcus Shawcroft
> ; Kyrylo Tkachov
> Subject: Re: [PATCH 5/8]AArch64 aarch64: Make existing V2HF be usable.
>
> Tamar
On Tue, Dec 6, 2022 at 11:47 AM Jakub Jelinek wrote:
>
> Hi!
>
> With -msoft-float we ICE on __bf16 comparisons, because the
> insns we want to use under the hood (cbranchsf4 and cstoresf4)
> after performing the fast extensions aren't available.
>
> The following patch copies the conditions from
1 - 100 of 154 matches
Mail list logo
