I've been under the weather so I took a few days break, I honestly was
also very reluctant to pick it back up. The current problem is what I
like to call "not friendly", but I am back at it now.
> > I don't understand what this means exactly, under what circumstances
> > would find the member
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111974
Sam James changed:
What|Removed |Added
CC||sjames at gcc dot gnu.org
--- Comment #5
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112112
--- Comment #2 from Andrew Pinski ---
One thing you should note (most likely not an issue here) is that plain char
can default to signed or unsigned depending on the arch/abi .
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112112
--- Comment #1 from 김대영 <22s302h0659 at sonline20 dot sen.go.kr> ---
Created attachment 56320
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56320=edit
bug_Poc Codes.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112112
Bug ID: 112112
Summary: Improper Arithmetic Type Conversion in
s390x-linux-gnu-gcc
Product: gcc
Version: 11.4.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112111
Bug ID: 112111
Summary: Improper Arithmetic Type Conversion in
s390x-linux-gnu-gcc
Product: gcc
Version: 11.4.0
Status: UNCONFIRMED
Severity: normal
On 10/27/23 14:31, Patrick O'Neill wrote:
Hi Fei,
A recent change to GCC [1] updated the the registers in the cm.push and
cm.pop insns for these testcases:
|FAIL: gcc.target/riscv/rv32i_zcmp.c -Os check-function-bodies test1
FAIL: gcc.target/riscv/rv32i_zcmp.c -Os check-function-bodies
On 10/27/23 14:31, Patrick O'Neill wrote:
Hi Fei,
A recent change to GCC [1] updated the the registers in the cm.push and
cm.pop insns for these testcases:
|FAIL: gcc.target/riscv/rv32i_zcmp.c -Os check-function-bodies test1
FAIL: gcc.target/riscv/rv32i_zcmp.c -Os check-function-bodies
sew64_scalar_helper is handling SEW64 vx instruction pattern on RV32 system.
According to RVV ISA, we can directly use vx instruction of SEW64 on RV32 system
since RV32 GR reg is 32bit.
Consider this following case:
vsetvl e64m1
vadd.vx v,v,x
will be transform by sew64_scalar_helper:
vsetvl
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111703
Patrick Palka changed:
What|Removed |Added
CC||ppalka at gcc dot gnu.org
--- Comment
On Fri, 27 Oct 2023, Patrick Palka wrote:
> On Fri, 27 Oct 2023, Jason Merrill wrote:
>
> > On 10/27/23 15:55, Patrick Palka wrote:
> > > With the previous two patches in place, we can now extend our
> > > deletedness diagnostic to note the other considered candidates, e.g.:
> > >
> > >
On Fri, 27 Oct 2023, Jason Merrill wrote:
> On 10/27/23 15:55, Patrick Palka wrote:
> > With the previous two patches in place, we can now extend our
> > deletedness diagnostic to note the other considered candidates, e.g.:
> >
> >deleted16.C: In function 'int main()':
> >
On 8/25/23 16:49, Jakub Jelinek wrote:
Hi!
This paper voted in as DR makes some multi-character literals ill-formed.
'abcd' stays valid, but e.g. 'á' is newly invalid in UTF-8 exec charset
while valid e.g. in ISO-8859-1, because it is a single character which needs
2 bytes to be encoded.
The
On Fri, Oct 27, 2023 at 4:00 AM Iain Sandoe wrote:
>
> Hi Richard,
>
> > On 26 Oct 2023, at 21:00, Iain Sandoe wrote:
>
> >> On 26 Oct 2023, at 20:49, Richard Sandiford
> >> wrote:
> >>
> >> Iain Sandoe writes:
> >>> This was written before Thomas' modification to the ELF-handling to allow
>
On 10/27/23 10:16, Bernhard Reutner-Fischer wrote:
On Wed, 25 Oct 2023 16:41:07 +0530
Ajit Agarwal wrote:
On 25/10/23 2:19 am, Vineet Gupta wrote:
On 10/24/23 13:36, rep.dot@gmail.com wrote:
As said, I don't see why the below was not cleaned up before the V1 submission.
Iff it breaks
Snapshot gcc-12-20231027 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/12-20231027/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 12 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
On 10/27/23 15:55, Patrick Palka wrote:
With the previous two patches in place, we can now extend our
deletedness diagnostic to note the other considered candidates, e.g.:
deleted16.C: In function 'int main()':
deleted16.C:10:4: error: use of deleted function 'void f(int)'
10 |
On 10/27/23 15:55, Patrick Palka wrote:
New in patch 1/3:
* consistently use "non-viable" instead of "unviable"
throughout
* make 'champ' and 'challenger' in 'tourney' be z_candidate**
to simplify moving 'champ' to the front of the list. drive-by
cleanups in tourney,
On Fri, Oct 27, 2023 at 2:12 PM David Malcolm wrote:
>
> On Fri, 2023-10-27 at 12:48 -0700, Andrew Pinski wrote:
> > Hi David and others,
> > I am in the process of improving phi-opt and moving what was
> > handled
> > in value_replacement to match-and-simplify and ran into a few
> > failures
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80454
Barnabás Pőcze changed:
What|Removed |Added
CC||pobrn at protonmail dot com
---
On Fri, 2023-10-27 at 12:48 -0700, Andrew Pinski wrote:
> Hi David and others,
> I am in the process of improving phi-opt and moving what was
> handled
> in value_replacement to match-and-simplify and ran into a few
> failures
> in the analyzer testsuite.
> For an example
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112107
Sergei Trofimovich changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
Hey,
I trust this message finds you well. I'm writing to propose a mutually
beneficial collaboration. I've been impressed by the quality and relevance
of your content, and I believe our websites share a common interest.
I'd like to kindly request that you consider placing a link to my website,
Hi!
To close the loop here:
On 2023-09-27T00:25:16+0200, I wrote:
> On 2023-09-20T13:59:53+0200, Arthur Cohen wrote:
>> From: Pierre-Emmanuel Patry
>>
>> Define the libgrust directory as a host compilation module as well as
>> for targets.
>
>> --- a/Makefile.def
>> +++ b/Makefile.def
>> @@
Hi!
To close the loop here:
On 2023-09-27T00:25:16+0200, I wrote:
> On 2023-09-20T13:59:53+0200, Arthur Cohen wrote:
>> From: Pierre-Emmanuel Patry
>>
>> Define the libgrust directory as a host compilation module as well as
>> for targets.
>
>> --- a/Makefile.def
>> +++ b/Makefile.def
>> @@
On Fri, 27 Oct 2023, Patrick Palka wrote:
> On Fri, 27 Oct 2023, Patrick Palka wrote:
>
> > On Fri, 20 Oct 2023, Jason Merrill wrote:
> >
> > > Tested x86_64-pc-linux-gnu, applying to trunk. Patrick, sorry I didn't
> > > apply
> > > this sooner.
> > >
> > > -- 8< --
> > >
> > > In r13-3766
On Fri, 27 Oct 2023, Patrick Palka wrote:
> On Fri, 20 Oct 2023, Jason Merrill wrote:
>
> > Tested x86_64-pc-linux-gnu, applying to trunk. Patrick, sorry I didn't
> > apply
> > this sooner.
> >
> > -- 8< --
> >
> > In r13-3766 I changed the logic at the end of tourney to avoid redundant
> >
Hi!
Short Friday evening status update:
On 2023-10-27T16:20:34+0200, I wrote:
> Short Friday afternoon status update:
>
> On 2023-10-27T08:51:12+0100, Iain Sandoe wrote:
>>> On 26 Oct 2023, at 09:21, Thomas Schwinge wrote:
>>> First, I've pushed into GCC upstream Git branch
Hi!
Short Friday evening status update:
On 2023-10-27T16:20:34+0200, I wrote:
> Short Friday afternoon status update:
>
> On 2023-10-27T08:51:12+0100, Iain Sandoe wrote:
>>> On 26 Oct 2023, at 09:21, Thomas Schwinge wrote:
>>> First, I've pushed into GCC upstream Git branch
On Fri, 20 Oct 2023, Jason Merrill wrote:
> Tested x86_64-pc-linux-gnu, applying to trunk. Patrick, sorry I didn't apply
> this sooner.
>
> -- 8< --
>
> In r13-3766 I changed the logic at the end of tourney to avoid redundant
> comparisons, but the change also meant skipping any less-good
New in patch 1/3:
* consistently use "non-viable" instead of "unviable"
throughout
* make 'champ' and 'challenger' in 'tourney' be z_candidate**
to simplify moving 'champ' to the front of the list. drive-by
cleanups in tourney, including renaming 'champ_compared_to_predecessor'
During overload resolution, we sometimes outright ignore a function in
the overload set and leave no trace of it in the candidates list, for
example when we find a perfect non-template candidate we discard all
function templates, or when the callee is a template-id we discard all
non-template
With the previous two patches in place, we can now extend our
deletedness diagnostic to note the other considered candidates, e.g.:
deleted16.C: In function 'int main()':
deleted16.C:10:4: error: use of deleted function 'void f(int)'
10 | f(0);
| ~^~~
deleted16.C:5:6: note:
On 10/20/23 07:52, Filip Kastl wrote:
On Fri 2023-10-20 15:50:25, Filip Kastl wrote:
Bootstraped and tested* on x86_64-pc-linux-gnu.
* One testcase (pr79691.c) did regress. However that is because the test is
dependent on a certain variable not being copy propagated. I will go into more
On 10/23/23 02:37, Florian Weimer wrote:
Current glibc headers only declare fputs_unlocked for _GNU_SOURCE,
so define it to obtain an official prototype.
Add a fallback prototype declaration for other systems that do not
have fputs_unlocked. This seems to the most straightforward approach
On Thu, 26 Oct 2023 at 23:40, Gerald Pfeifer wrote:
>
> On Thu, 26 Oct 2023, Sam James wrote:
> > These options both enabled more checking within the C++ standard library
> > and can expose errors in submitted code.
>
> This is a good addition, thank you! I was going to approve/push, but it's
>
On 10/23/23 03:54, pan2...@intel.com wrote:
From: Pan Li
The vsetvl asm check is unnecessary for the vector convert. We
should be focus for constrait and leave the vsetvl test to the
vsetvl pass.
gcc/testsuite/ChangeLog:
* gcc.target/riscv/rvv/autovec/unop/cvt-0.c: Remove the
Hi David and others,
I am in the process of improving phi-opt and moving what was handled
in value_replacement to match-and-simplify and ran into a few failures
in the analyzer testsuite.
For an example c-c++-common/analyzer/inlining-3-multiline.c (and
c-c++-common/analyzer/inlining-3.c) now
Hi David,
David Faust writes:
> On 10/26/23 08:08, Cupertino Miranda wrote:
>>
>> Changes from v1:
>> - Fixed Davids remarks on initial patch.
>> - Fixed mistake with deleted '*'.
>>
>> Changes from v2:
>> - Reversed return value for bpf_const_not_ok_for_debug_p function.
>
> Hmm..
>
>>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104555
anlauf at gcc dot gnu.org changed:
What|Removed |Added
CC||anlauf at gcc dot gnu.org
The following patch fixes i686 bootstrap failure because of my recent
patch:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112107
commit 7361b49d7fa3624cb3f1f825a22607d9d31986e5
Author: Vladimir N. Makarov
Date: Fri Oct 27 14:50:40 2023 -0400
[RA]: Fixing i686 bootstrap failure because
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112107
--- Comment #10 from CVS Commits ---
The trunk branch has been updated by Vladimir Makarov :
https://gcc.gnu.org/g:4d3d2cdb574488223d023b590c3a34ddd93f4dae
commit r14-4986-g4d3d2cdb574488223d023b590c3a34ddd93f4dae
Author: Vladimir N. Makarov
After working with Sam off-list (thanks) I managed to get hppa to
build. Initially it looked as if hppa just had a very small number of
instruction patterns so we wouldn't generate all 10 output files.
However, the actual issue (which we will only hit with a low
pattern count) was with counting
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112107
--- Comment #9 from Vladimir Makarov ---
(In reply to Sergei Trofimovich from comment #8)
> bootstrap with default options did not fail for me either. I had to use
> --enable-checking=release to trigger the failure. I wonder if it exposes the
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104649
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Resolution|--- |FIXED
On 10/27/23 11:02, Jeff Law wrote:
On 10/27/23 11:56, Patrick O'Neill wrote:
GCC recently changed to emit __riscv_restore_5 which causes this
testcase to fail.
This patch updates the regex to be more robust to change by accepting
any number after __riscv_save_ and __riscv_restore_.
Okay, thanks for the explanation.
We will keep this in mind.
Qing
> On Oct 27, 2023, at 1:19 PM, Kees Cook wrote:
>
> On Fri, Oct 27, 2023 at 03:10:22PM +, Qing Zhao wrote:
>> Since the dynamic array support is quite important to the kernel (is this
>> true, Kees? ),
>> We might need to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112107
--- Comment #8 from Sergei Trofimovich ---
bootstrap with default options did not fail for me either. I had to use
--enable-checking=release to trigger the failure. I wonder if it exposes the
failure for you as well.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112107
--- Comment #7 from Vladimir Makarov ---
Sorry for inconvenience because of my patch.
I reproduced the bug with the reproducer using stage1 gcc although strangely
the standard bootstrap works ok for me on i686 debian.
I think I know the
On 10/27/23 11:56, Patrick O'Neill wrote:
GCC recently changed to emit __riscv_restore_5 which causes this
testcase to fail.
This patch updates the regex to be more robust to change by accepting
any number after __riscv_save_ and __riscv_restore_.
gcc/testsuite/ChangeLog:
*
GCC recently changed to emit __riscv_restore_5 which causes this
testcase to fail.
This patch updates the regex to be more robust to change by accepting
any number after __riscv_save_ and __riscv_restore_.
gcc/testsuite/ChangeLog:
* gcc.target/riscv/stack_save_restore_2.c: Accept any
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104649
--- Comment #7 from Steve Kargl ---
On Fri, Oct 27, 2023 at 05:18:02PM +, cvs-commit at gcc dot gnu.org wrote:
>
>
> commit r14-4983-gc6430d3e6d3279c7e4be9d189031a17bb3dec347
> Author: Harald Anlauf
> Date: Thu Oct 26 22:32:35 2023
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109131
Alexey changed:
What|Removed |Added
CC||alexey.lapshin at espressif
dot co
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112110
Gaius Mulley changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112110
Gaius Mulley changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
On 10/27/23 11:39, Andrew Waterman wrote:
On Fri, Oct 27, 2023 at 6:44 AM Jeff Law wrote:
On 10/27/23 01:37, juzhe.zh...@rivai.ai wrote:
LGTM from my side.
The original integer division COST seems too low.
Almost certainly, though there may be good reasons why it was initially
set so
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112110
--- Comment #1 from CVS Commits ---
The master branch has been updated by Gaius Mulley :
https://gcc.gnu.org/g:32cc0b82a3c2e38caa9f2266d4ba375ccb1fe9cc
commit r14-4984-g32cc0b82a3c2e38caa9f2266d4ba375ccb1fe9cc
Author: Gaius Mulley
Date:
On 10/27/23 11:34, Patrick O'Neill wrote:
On 8/25/23 15:36, Jeff Law wrote:
Spurred by Jivan's patch and a desire for cleaner testresults, I went
ahead and make the stack_save_restore tests independent of the precise
stack size by using a regexp.
Pushed to the trunk.
Jeff
Hi Jeff, A
On Fri, Oct 27, 2023 at 6:44 AM Jeff Law wrote:
>
>
>
> On 10/27/23 01:37, juzhe.zh...@rivai.ai wrote:
> > LGTM from my side.
> >
> > The original integer division COST seems too low.
> Almost certainly, though there may be good reasons why it was initially
> set so low. I'm generally hesitant
On 8/25/23 15:36, Jeff Law wrote:
Spurred by Jivan's patch and a desire for cleaner testresults, I went
ahead and make the stack_save_restore tests independent of the precise
stack size by using a regexp.
Pushed to the trunk.
Jeff
Hi Jeff, A recent change that I'm still bisecting [1]
On Fri, Oct 27, 2023 at 6:55 AM Jeff Law wrote:
>
>
>
> On 10/27/23 01:49, Robin Dapp wrote:
> >> @@ -346,7 +346,7 @@ static const struct riscv_tune_param rocket_tune_info
> >> = {
> >> {COSTS_N_INSNS (4), COSTS_N_INSNS (5)}, /* fp_mul */
> >> {COSTS_N_INSNS (20), COSTS_N_INSNS (20)},
On Fri, Oct 27, 2023 at 03:10:22PM +, Qing Zhao wrote:
> Since the dynamic array support is quite important to the kernel (is this
> true, Kees? ),
> We might need to include such support into our design in the beginning.
tl;dr: We don't need "dynamic array support" in the 1st version of
ACLE has added intrinsics to bridge between SVE and Neon.
The NEON_SVE Bridge adds intrinsics that allow conversions between NEON and
SVE vectors.
This patch adds support to GCC for the following 3 intrinsics:
svset_neonq, svget_neonq and svdup_neonq
gcc/ChangeLog:
* config.gcc: Adds
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104649
--- Comment #6 from CVS Commits ---
The master branch has been updated by Harald Anlauf :
https://gcc.gnu.org/g:c6430d3e6d3279c7e4be9d189031a17bb3dec347
commit r14-4983-gc6430d3e6d3279c7e4be9d189031a17bb3dec347
Author: Harald Anlauf
Date:
On Wed, 25 Oct 2023 16:41:07 +0530
Ajit Agarwal wrote:
> On 25/10/23 2:19 am, Vineet Gupta wrote:
> > On 10/24/23 13:36, rep.dot@gmail.com wrote:
> >> As said, I don't see why the below was not cleaned up before the V1
> >> submission.
> >> Iff it breaks when manually CSEing,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112088
Andrew Stubbs changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
On 20/10/2023 12:51, Andrew Stubbs wrote:
I've committed this patch that allows building binaries for AMD gfx1030
GPUs. I can't actually test it, however, so somebody else will have to
debug it (or wait for me to get my hands on a device). Richi reports
that it does not execute correctly, as
This trivial patch adds the "operands" keyword to the condition in a
couple of patterns that cause warnings about "missing" mode specifiers.
With the iterators, there were a large number of warnings about these
cases that have now been silenced.
Andrewamdgcn: silence warnings
The operands
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112088
--- Comment #2 from CVS Commits ---
The master branch has been updated by Andrew Stubbs :
https://gcc.gnu.org/g:9f3c4c673d769bd3f1d504d85b743ba250e68d7b
commit r14-4982-g9f3c4c673d769bd3f1d504d85b743ba250e68d7b
Author: Andrew Stubbs
Date:
About where we should insert the new __builtin_with_access_and_size:
> On Oct 26, 2023, at 2:54 PM, Qing Zhao wrote:
>
>
>
>> On Oct 26, 2023, at 10:05 AM, Richard Biener
>> wrote:
>>
>>
>>
>>> Am 26.10.2023 um 12:14 schrieb Martin Uecker :
>>>
>>> Am Donnerstag, dem 26.10.2023 um
A minor tweak to the documentation, to use git rather than cvs to obtain
the latest version of newlib. Ok for mainline?
2023-10-27 Roger Sayle
* htdocs/simtest-howto.html: Use git to obtain newlib.
Cheers,
Roger
--
diff --git a/htdocs/simtest-howto.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112099
--- Comment #2 from Utkarsh Saxena ---
Great. The core issue completely captures this issue. Then I will wait for a
resolution there.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112107
--- Comment #6 from Sergei Trofimovich ---
(In reply to Sergei Trofimovich from comment #5)
> Bisected down to r14-4943-g8d2130a4e5ce36 "[RA]: Modfify cost calculation
> for dealing with equivalences"
Sorry, pasted wrong hash. That should be a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112107
Sergei Trofimovich changed:
What|Removed |Added
CC||vmakarov at gcc dot gnu.org,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112110
Bug ID: 112110
Summary: fails to build on freebsd when compiling wrapclock.cc
in wrapclock_timezone attempting to return timezone
Product: gcc
Version: 14.0
Status:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111950
--- Comment #4 from Tamar Christina ---
> turning c_I_lsm.18_38 into a fully invariant reduction def which likely isn't
supported - we had bugs here in the past with not relevant but live stmts.
But if-conversion also performs the (now valid)
Jeff Law writes:
> On 10/24/23 04:15, Richard Sandiford wrote:
>> An inline asm with multiple output operands is represented as a
>> parallel set in which the SET_SRCs are the same (shared) ASM_OPERANDS.
>> insn_propgation didn't account for this, and instead propagated
>> into each ASM_OPERANDS
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111929
--- Comment #12 from CVS Commits ---
The master branch has been updated by Patrick Palka :
https://gcc.gnu.org/g:6ff8b93c7b0bf3913fb7754f9985e7e31c46d89c
commit r14-4979-g6ff8b93c7b0bf3913fb7754f9985e7e31c46d89c
Author: Patrick Palka
Date:
N.B. we currently don't diagnose 'new A(1)' below ultimately because
when in a template context our valid ctor call checking only happens for
type_build_ctor_call types.
-- >8 --
gcc/testsuite/ChangeLog:
* g++.dg/template/new14.C: New test.
---
gcc/testsuite/g++.dg/template/new14.C |
In some configurations of our validation setup, we always call the
compiler with -Wl,-rpath=XXX, which instructs the driver to invoke the
linker if none of -c, -S or -E is used.
This happens to be the case in the PCH tests, where dg-flags-pch sets
dg-do-what-default to precompile.
This works
> On Oct 27, 2023, at 10:53 AM, Martin Uecker wrote:
>
> Am Freitag, dem 27.10.2023 um 14:32 + schrieb Qing Zhao:
>>
>>> On Oct 27, 2023, at 3:21 AM, Martin Uecker wrote:
>>>
>>> Am Donnerstag, dem 26.10.2023 um 19:57 + schrieb Qing Zhao:
I guess that what Kees wanted, ""fill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111530
Gaius Mulley changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
Hello,
Today I have noticed that latest GCC documentation still has
(https://gcc.gnu.org/onlinedocs/gcc/x86-Options.html#index-mtune-17)
-mtune=cpu-type
... ...
‘intel’
Produce code optimized for the most current Intel processors, which are Haswell
and Silvermont for this version of GCC. ...
On 10/20/23 13:05, Florian Weimer wrote:
gcc/testsuite/
* gcc.c-torture/compile/2412-2.c (f): Call
__builtin_strleninstead of strlen.
* gcc.c-torture/compile/2427-1.c (FindNearestPowerOf2):
Declare.
* gcc.c-torture/compile/2802-1.c
v2: Formatting and nits fixed.
Follow up patch to arm: Use deltas for Arm switch tables
This patch moves the switch tables for Arm from the .text section
into the .rodata section.
gcc/ChangeLog:
* config/arm/aout.h: Change to use the Lrtx label.
* config/arm/arm.h
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111530
--- Comment #3 from CVS Commits ---
The master branch has been updated by Gaius Mulley :
https://gcc.gnu.org/g:e5f6a5ad7ceece5238fc3d63f7ea92574df4264d
commit r14-4976-ge5f6a5ad7ceece5238fc3d63f7ea92574df4264d
Author: Gaius Mulley
Date:
Am Freitag, dem 27.10.2023 um 14:32 + schrieb Qing Zhao:
>
> > On Oct 27, 2023, at 3:21 AM, Martin Uecker wrote:
> >
> > Am Donnerstag, dem 26.10.2023 um 19:57 + schrieb Qing Zhao:
> > > I guess that what Kees wanted, ""fill the array without knowing the
> > > actual final size" code
On 10/24/23 04:15, Richard Sandiford wrote:
An inline asm with multiple output operands is represented as a
parallel set in which the SET_SRCs are the same (shared) ASM_OPERANDS.
insn_propgation didn't account for this, and instead propagated
into each ASM_OPERANDS individually. This meant
On 10/26/23 12:50, Yangyu Chen wrote:
This patch fixes an issue with the cost on "int_div" in various RISC-V
tune parameters including those for Rocket, SiFive U7 series, and T-Head
C906. This incorrect cost value interferes with the optimization process.
For example, it prevents the
On 10/27/23 08:22, Roger Sayle wrote:
This patch improves the code generated by the ARC back-end for CPUs
without a barrel shifter but with -mswap. The -mswap option provides
a SWAP instruction that implements SImode rotations by 16, but also
logical shift instructions (left and right) by
> On Oct 27, 2023, at 3:21 AM, Martin Uecker wrote:
>
> Am Donnerstag, dem 26.10.2023 um 19:57 + schrieb Qing Zhao:
>> I guess that what Kees wanted, ""fill the array without knowing the actual
>> final size" code pattern”, as following:
>>
struct foo *f;
char *p;
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111950
--- Comment #3 from Tamar Christina ---
(In reply to Richard Biener from comment #2)
> For the epilog LC-SSA we lack the correct SSA name for the skip edge:
>
>
> [local count: 16140304]:
> # prephitmp_78 = PHI
> # c_I_lsm.18_79 = PHI
> #
Hi!
Richard, as the original author of 'SSA_NAME_POINTS_TO_READONLY_MEMORY':
2018 commit 6214d5c7e7470bdd5ecbeae668c2522551bfebbc (Subversion r263958)
"Move const_parm trick to generic code"; 'gcc/tree.h':
/* Nonzero if this SSA_NAME is known to point to memory that may not
be written
On Fri, 27 Oct 2023 at 16:19, Vladimir Makarov wrote:
>
>
> On 10/27/23 09:56, Christophe Lyon wrote:
> > Hi Vladimir,
> >
> > On Thu, 26 Oct 2023 at 16:00, Vladimir Makarov
> > wrote:
> >> This is the second attempt to improve RA cost calculation for pseudos
> >> with equivalences. The patch
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112109
Bug ID: 112109
Summary: Missing riscv vectorized strcmp (and other) expanders
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
The following patch fixes one aarch64 GCC test failure resulted from my
previous patch dealing with reg equivalences.
The patch was successfully bootstrapped and tested on x86-64, aarch64,
ppc64le.
commit 9b03e1d20c00dca215b787a5e959db473325b660
Author: Vladimir N. Makarov
Date: Fri Oct
This patch improves the code generated by the ARC back-end for CPUs
without a barrel shifter but with -mswap. The -mswap option provides
a SWAP instruction that implements SImode rotations by 16, but also
logical shift instructions (left and right) by 16 bits. Clearly these
are also useful
Hi!
Short Friday afternoon status update:
On 2023-10-27T08:51:12+0100, Iain Sandoe wrote:
>> On 26 Oct 2023, at 09:21, Thomas Schwinge wrote:
>> First, I've pushed into GCC upstream Git branch devel/rust/libgrust-v2
>> the "v2" libgrust changes as posted by Arthur, so that people can easily
>>
Hi!
Short Friday afternoon status update:
On 2023-10-27T08:51:12+0100, Iain Sandoe wrote:
>> On 26 Oct 2023, at 09:21, Thomas Schwinge wrote:
>> First, I've pushed into GCC upstream Git branch devel/rust/libgrust-v2
>> the "v2" libgrust changes as posted by Arthur, so that people can easily
>>
On 10/27/23 09:56, Christophe Lyon wrote:
Hi Vladimir,
On Thu, 26 Oct 2023 at 16:00, Vladimir Makarov wrote:
This is the second attempt to improve RA cost calculation for pseudos
with equivalences. The patch explanation is in the log message.
The patch was successfully bootstrapped and
1 - 100 of 192 matches
Mail list logo
