Hi!
I'd like to ping this patch for acknowledgement from the Ada team.
We have successfully compiled a cross-native toolchain with Ada enabled
for loongarch64-linux-gnuf64 (or loongarch64-linux-gnu), and have run the
regtests with the following results:
While the failures are being worked on,
Hoist want_to_gcse_p () calls rtx_cost () to compute max distance for
hoist candidates. For a simple const (say 6 which needs seperate insn "LI 6")
backend currently returns 0, causing Hoist to bail and elide GCSE.
Note that constants requiring more than 1 insns to setup were working
fine since
Hi Jivan,
On 8/24/23 08:45, Jivan Hakobyan via Gcc-patches wrote:
This patch fixes failing stack_save_restore_1/2 test cases.
After 6619b3d4c15c commit size of the frame was changed.
gcc/testsuite/ChangeLog:
* gcc.target/riscv/stack_save_restore_1.c: Update frame size
*
gcc/ChangeLog:
* ada/Makefile.rtl: Add LoongArch support.
* ada/libgnarl/s-linux__loongarch.ads: New.
* ada/libgnat/system-linux-loongarch.ads: New.
* config/loongarch/loongarch.h: mark normalized options
passed from driver to gnat1 as explicit for
vpmaskmov{d,q} is available for TARGET_AVX2, vmaskmov{ps,ps} is
available for TARGET_AVX, w/o TARGET_AVX2, we can use vmaskmov{ps,pd}
for VI48_128_256
Bootstrapped and regtested on x86_64-pc-linux{-m32,}.
Ready push to trunk.
gcc/ChangeLog:
PR target/19
* config/i386/sse.md
On 8/25/23 12:01, Lulu Cheng wrote:
Since the slt instruction does not distinguish between 32-bit and 64-bit
operations
under the LoongArch 64-bit architecture, if the operands of slt are of SImode,
symbol
expansion is required before operation.
Hint:“符号扩展” is "sign extension" (as noun) or
Since the slt instruction does not distinguish between 32-bit and 64-bit
operations
under the LoongArch 64-bit architecture, if the operands of slt are of SImode,
symbol
expansion is required before operation.
But similar to the following test case, symbol expansion can be omitted:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=36
--- Comment #1 from JuzheZhong ---
Hi, Richi.
It faild at RISC-V scatter store cases:
When trying to generate gimple build:
...
.MASK_LEN_SCATTER_STORE (vectp_y.28_130, { 0, 2, 4, ... }, 1, vect__25.27_127,
mask__26.20_117, _135, 0);
...
On 2023-08-25 03:06, libreknight wrote:
> Greetings.
>
> I have come across erroneous behavior whilst comparing optimizations
> performed by different compilers. Said behavior persists through
> different versions of GCC and flags. The output from GCC is incorrect
> and diverges from all
On 8/24/23 12:56 AM, Kewen.Lin wrote:
> By looking into the uses of function rs6000_pcrel_p, I think we can
> just replace it with TARGET_PCREL. Previously we don't require PCREL
> unset for any unsupported target/OS, so we need rs6000_pcrel_p() to
> ensure it's really supported in those use
On Thu, Aug 24, 2023 at 8:06 PM libreknight via Gcc-bugs
wrote:
>
> Greetings.
>
> I have come across erroneous behavior whilst comparing optimizations
> performed by different compilers. Said behavior persists through
> different versions of GCC and flags. The output from GCC is incorrect
> and
This patch refactors the Phase 3 (Demand fusion) and rename it into Earliest
fusion.
I do the refactor for the following reasons:
1. Current implementation of phase 3 is doing too many things which makes the
code quality
quite messy and not easy to maintain.
2. The demand fusion I do
Greetings.
I have come across erroneous behavior whilst comparing optimizations
performed by different compilers. Said behavior persists through
different versions of GCC and flags. The output from GCC is incorrect
and diverges from all compilers.
In order to reproduce aforementioned behavior,
lgtm
On Fri, Aug 25, 2023 at 9:49 AM Pan Li via Gcc-patches
wrote:
>
> From: Pan Li
>
> There will be a case like below for intrinsic and autovec combination.
>
> vfadd RTZ <- intrinisc static rounding
> vfnmadd <- autovec/autovec-opt
>
> The autovec generated vfnmadd should take DYN
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49
Andrew Pinski changed:
What|Removed |Added
Component|tree-optimization |middle-end
Summary|bool0 !=
On 8/24/23 12:35 PM, Michael Meissner wrote:
> On Thu, Jul 20, 2023 at 10:05:28AM +0530, jeevitha wrote:
>> gcc/
>> PR target/110411
>> * config/rs6000/rs6000.h (enum rs6000_builtin_type_index): Add fields
>> to hold PTImode type.
>> * config/rs6000/rs6000-builtin.cc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49
Andrew Pinski changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |pinskia at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49
Bug ID: 49
Summary: bool0 != bool1 should be convert into bool0 ^ bool1
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Keywords: missed-optimization
Severity:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48
Andrew Pinski changed:
What|Removed |Added
Last reconfirmed||2023-08-25
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48
Bug ID: 48
Summary: Missing boolean optimizations due to comparisons
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Keywords: missed-optimization
Severity:
V2 changes: Address comments from Robin.
Hi,
This patch adds conditional sign/zero extension and truncation autovec
patterns by combining convert and vcond_mask patterns.
For quad truncation, two vncvt instructions are generated. This patch
combine the second vncvt and vmerge to form a masked
Committed.
gcc/ChangeLog:
* config/riscv/riscv-vsetvl.cc (pass_vsetvl::compute_local_properties):
Add early continue.
---
gcc/config/riscv/riscv-vsetvl.cc | 2 ++
1 file changed, 2 insertions(+)
diff --git a/gcc/config/riscv/riscv-vsetvl.cc b/gcc/config/riscv/riscv-vsetvl.cc
index
From: Pan Li
There will be a case like below for intrinsic and autovec combination.
vfadd RTZ <- intrinisc static rounding
vfnmadd <- autovec/autovec-opt
The autovec generated vfnmadd should take DYN mode, and the
frm must be restored before the vfnmadd insn. This patch
would like to fix
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=47
Andrew Pinski changed:
What|Removed |Added
Last reconfirmed||2023-08-25
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=47
Bug ID: 47
Summary: bitwise_inverted_equal_p can be used in the `(x | y) &
(~x ^ y)` pattern to catch more
Product: gcc
Version: 14.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=46
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=46
Bug ID: 46
Summary: Some patterns in match.pd are no longer needed
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Keywords: compile-time-hog
Severity: enhancement
Thanks Kito, will commit it after VFMADD, VFMSAC.
Pan
-Original Message-
From: Kito Cheng
Sent: Thursday, August 24, 2023 10:24 PM
To: Li, Pan2
Cc: gcc-patches@gcc.gnu.org; juzhe.zh...@rivai.ai; Wang, Yanzhang
Subject: Re: [PATCH v1] RISC-V: Support rounding mode for VFNMSAC/VFNMSUB
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110628
--- Comment #10 from Hans-Peter Nilsson ---
(In reply to Hans-Peter Nilsson from comment #9)
> (In reply to Jan Hubicka from comment #8)
> > patch posted
> > https://gcc.gnu.org/pipermail/gcc-patches/2023-August/628231.html
>
> Yay! I stand
> Date: Wed, 23 Aug 2023 11:10:02 +0200
> From: Jan Hubicka via Gcc-patches
> Hi,
> this patch adds missing profile update to maybe_optimize_range_tests.
[...]
> Jakub, it seems that the code is originally yours. Any idea why those are
> not turned to
> constant true or false conditionals?
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109662
Jerry DeLisle changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REOPENED
On 8/24/23 11:28, Palmer Dabbelt wrote:
Reviewed-by: Palmer Dabbelt
I think Joern is still looking into fixing up all these explicit ISA
strings in the tests, but I don't see any reason to block fixing
failing tests on that.
Thanks!
Committed
Patrick
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=27
Hongyu Wang changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=27
--- Comment #2 from CVS Commits ---
The releases/gcc-13 branch has been updated by Hongyu Wang
:
https://gcc.gnu.org/g:bb791011b39813bc7b6fdd0d9831247ace199615
commit r13-7758-gbb791011b39813bc7b6fdd0d9831247ace199615
Author: Hongyu Wang
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=27
--- Comment #1 from CVS Commits ---
The master branch has been updated by Hongyu Wang :
https://gcc.gnu.org/g:e62fe74e5af913079ba296c74759cd74c0759e8e
commit r14-3473-ge62fe74e5af913079ba296c74759cd74c0759e8e
Author: Hongyu Wang
Date: Thu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111022
--- Comment #6 from Jerry DeLisle ---
(In reply to john.harper from comment #5)
Thanks John, I had a moment to look at this. I know where to do the
implementation but I have not decided how yet.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=19
--- Comment #3 from Hongtao.liu ---
> I see, we can add an alternative like "noavx2,avx2" to generate
> vmaskmovps/pd when avx2 is not available for integer.
It's better to change assmeble output as
27423 if (TARGET_AVX2)
27424return
On 8/24/23 2:28 PM, Harald Anlauf via Fortran wrote:
Dear all,
the attached patch adds stricter bounds-checking for DATA statements
with implied-do. I chose to allow overindexing (for arrays of rank
greater than 1) for -std=legacy, as there might be codes in the wild
that need this (and this
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110823
--- Comment #5 from Paul Eggert ---
Also see bug 43 for a related performance issue, which is perhaps more
important given the current state of bleeding-edge GNU diffutils.
On Thu, Aug 24, 2023 at 5:05 PM Hongyu Wang via Gcc-patches
wrote:
>
> Hi,
>
> For PR27, the wrong code was caused by wrong expander for maskz.
> correct the parameter order for avx512ne2ps2bf16_maskz expander
>
> Bootstrapped/regtested on x86-64-pc-linux-gnu{m32,}.
> OK for master and
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=19
Hongtao.liu changed:
What|Removed |Added
CC||crazylht at gmail dot com
--- Comment #2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80770
--- Comment #3 from Andrew Pinski ---
For aarch64 we get this from combine:
```
Trying 8, 10 -> 12:
8: r92:SI=r96:QI#0&0x1
10: r93:SI=r92:SI^0x1
REG_DEAD r92:SI
12: zero_extract(r99:QI#0,0x1,0)=r93:SI
REG_DEAD r93:SI
Failed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44
Eric Gallager changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105369
Eric Gallager changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
> From: benjamin priour
>
> Hi,
>
> Below the first batch of a serie of patches to transition
> the analyzer testsuite from gcc.dg/analyzer to c-c++-common/analyzer.
> I do not know how long this serie will be, thus the patch was not
> numbered.
>
> For the grand majority of the tests, the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106677
Andrew Pinski changed:
What|Removed |Added
Last reconfirmed||2023-08-24
Snapshot gcc-11-20230824 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/11-20230824/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 11 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44
--- Comment #2 from David Malcolm ---
See also bug 6906 and bug 57612
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=35095
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |ASSIGNED
CC|
Dear all,
the attached patch adds stricter bounds-checking for DATA statements
with implied-do. I chose to allow overindexing (for arrays of rank
greater than 1) for -std=legacy, as there might be codes in the wild
that need this (and this is accepted by some other compilers, while
NAG is strict
Related Discussion:
https://inbox.sourceware.org/gcc-patches/12fb5088-3f28-0a69-de1e-f387371a5...@gmail.com/
This patch updates the sync instructions to ensure that no insn is left
without a type attribute. Updates a total of 6 insns to have type "atomic"
Tested for regressions using rv32/64
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=45
Bug ID: 45
Summary: istream::operator>>(streambuf*) does not set gcount
Product: gcc
Version: 13.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=41
--- Comment #2 from Andrew Pinski ---
I think we should improve the toplevel configure to error out if including
errno.h fails.
So instead of:
```
echo "int main () { return 0; }" > conftest.c
```
We should do:
```
echo "#include " >
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44
--- Comment #1 from David Malcolm ---
See e.g.:
https://wiki.sei.cmu.edu/confluence/display/c/PRE31-C.+Avoid+side+effects+in+arguments+to+unsafe+macros
https://stackoverflow.com/questions/10593492/catching-assert-with-side-effects
cppcheck:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44
Bug ID: 44
Summary: RFE: could -fanalyzer warn about assertions that have
side effects?
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=07
--- Comment #6 from Zebediah Figura ---
(In reply to Zebediah Figura from comment #4)
> (In reply to Andrew Pinski from comment #3)
> > https://inbox.sourceware.org/gcc-patches/5969976.Bvae8NF9fS@polaris/
>
> Again, I'm not sure what you're
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94866
Uroš Bizjak changed:
What|Removed |Added
Target Milestone|--- |14.0
Status|ASSIGNED
Add new pattern involving vec_merge RTX that is produced by combine from the
combination of sse4_1_pinsrq and *movdi_internal:
7: r86:DI=0
8: r85:V2DI=vec_merge(vec_duplicate(r86:DI),r87:V2DI,0x2)
REG_DEAD r87:V2DI
REG_DEAD r86:DI
Successfully matched this instruction:
(set
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94866
--- Comment #9 from CVS Commits ---
The master branch has been updated by Uros Bizjak :
https://gcc.gnu.org/g:6dd73f0f00f454a05552b008a1d56560bd3f1d4a
commit r14-3471-g6dd73f0f00f454a05552b008a1d56560bd3f1d4a
Author: Uros Bizjak
Date: Thu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=43
--- Comment #3 from Andrew Pinski ---
_22 = *iter_57;
if (_22 >= 0)
goto ; [90.00%]
else
goto ; [10.00%]
[local count: 860067200]:
_76 = (long long unsigned int) _22;
_15 = sum_31 + _76;
goto ; [100.00%]
...
[local
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=42
Andrew Pinski changed:
What|Removed |Added
Component|rtl-optimization|tree-optimization
Keywords|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=41
--- Comment #1 from Jonathan Wakely ---
Looks like you don't have the 32-bit headers installed. See
https://gcc.gnu.org/wiki/FAQ#gnu_stubs-32.h
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=40
--- Comment #3 from Jonathan Wakely ---
But I don't know why -fno-deduce-init-list only affects the diagnostic for one
of the function templates.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=43
--- Comment #2 from Paul Eggert ---
Created attachment 55790
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55790=edit
asm code that's 38% faster on my platform
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=43
--- Comment #1 from Paul Eggert ---
Created attachment 55789
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55789=edit
asm code generated by gcc -O2 -S
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=40
--- Comment #2 from Jonathan Wakely ---
I think r0-112851-g15694fdd6d84db changed the diagnostic by making
-fno-deduce-init-list the default.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=43
Bug ID: 43
Summary: [missed optimization] unlikely code slows down
diffutils x86-64 ASCII processing
Product: gcc
Version: 13.1.1
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=42
--- Comment #1 from Manuel Lauss ---
This is fairly new, something after 4aa14ec7d5b25722e4d02c29c8c1e22dcc5a4915
("MATCH: [PR09] Fix bit_ior(cond,cond) when comparisons are fp") may have
caused this, since I was able to build mesa just 12
dit
compressed unreduced testcase
gcc version 14.0.0 20230824 (experimental)
721f7e2c4e5eed645593258624dd91e6c39f3bd2
g++ -m32 -O2 -march=znver4 -c gcc-14-mesa-aco-ice.ii
during GIMPLE pass: vect
../mesa-/src/amd/compiler/aco_insert_waitcnt.cpp: In function 'void
aco::insert_wait_states(Prog
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=41
Bug ID: 41
Summary: Compiling gcc-13.2.0 on Ubuntu 22.04.3 LTS, problem
asm-generic/errno.h
Product: gcc
Version: 13.2.0
Status: UNCONFIRMED
Severity:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=32
Patrick Palka changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org,
GCC maintainers:
Version 3, fixed the built-in instance names. Missed removing the "n"
the name. Added the tighter constraints on the predicates for the
define_insn. Updated the wording for the built-ins in the
documentation file. Changed the test file name again. Updated the
ChangeLog file,
Kewen, Peter:
> on 2023/8/17 08:19, Carl Love wrote:
> > GCC maintainers:
> >
> > Version 2, renamed the built-in instances. Changed the name of the
> > overloaded built-in. Added the missing documentation for the new
> > built-ins. Fixed typos. Changed name of the test. Updated the
> >
Now that MIN/MAX can sometimes be transformed into BIT_AND/BIT_IOR,
we should allow BIT_AND and BIT_IOR in the early phiopt.
Also we produce BIT_AND/BIT_IOR for things like `bool0 ? bool1 : 0`
which seems like a good thing to allow early on too.
OK? Bootstrapped and tested on x86_64-linux-gnu
In PR 106677, I noticed that on the trunk we were producing:
```
_25 = SR.116_117 == 0;
_27 = (unsigned char) _25;
_32 = _27 | SR.116_117;
```
>From `SR.115_117 != 0 ? SR.115_117 : 1`
Rather than:
```
_119 = MAX_EXPR <1, SR.115_117>;
```
Or (rather)
```
_119 = SR.115_117 | 1;
```
Due to
Even though this is handled by other code inside both VRP and CCP,
sometimes we want to optimize this outside of VRP and CCP.
An example is given in PR 106677 where phiopt will happen
after VRP (which removes a cast for a comparison) and then
phiopt will optimize the phi to be `a | 1` which can
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=40
Andrew Pinski changed:
What|Removed |Added
Last reconfirmed|2023-08-24 00:00:00 |
--- Comment #1 from Andrew Pinski
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=40
Marek Polacek changed:
What|Removed |Added
CC||mpolacek at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=40
Bug ID: 40
Summary: wrong error message
Product: gcc
Version: 12.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=32
Andrew Pinski changed:
What|Removed |Added
Known to work||8.5.0
Known to fail|
On Thu, 24 Aug 2023 11:04:59 PDT (-0700), Patrick O'Neill wrote:
Resolves failures like this on rv32gcv linux:
compiler exited with status 1
output is:
In file included from
/tc-baseline/build-linux-gcv/sysroot/usr/include/features.h:515,
from
Resolves failures like this on rv32gcv linux:
compiler exited with status 1
output is:
In file included from
/tc-baseline/build-linux-gcv/sysroot/usr/include/features.h:515,
from
/tc-baseline/build-linux-gcv/sysroot/usr/include/bits/libc-header-start.h:33,
from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=37
Andrew Pinski changed:
What|Removed |Added
Ever confirmed|0 |1
Known to fail|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92586
Paul Thomas changed:
What|Removed |Added
CC||pault at gcc dot gnu.org
--- Comment #11
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=39
palmer at gcc dot gnu.org changed:
What|Removed |Added
Last reconfirmed||2023-08-24
Ever
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=39
Bug ID: 39
Summary: RISC-V: improve scalar constants cost model
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
On Thu, Jul 20, 2023 at 10:05:28AM +0530, jeevitha wrote:
> Hi All,
>
> The following patch has been bootstrapped and regtested on powerpc64le-linux.
>
> When the user specifies PTImode as an attribute, it breaks. Created
> a tree node to handle PTImode types. PTImode attribute helps in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=37
Andrew Pinski changed:
What|Removed |Added
Summary|Wrong code at -O2/3 since |[12/13/14 Regression] Wrong
I've now prepared the patch to support following config:
--disable-libstdcxx-dual-abi --with-default-libstdcxx-abi=new
and so detected yet another problem with src/c++98/compatibility.cc. We
need basic_istream<>::ignore(streamsize) definitions that rely here but
not the rest of it.
François
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=38
Bug ID: 38
Summary: views::zip_transform is underconstrained for empty
range pack
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
>
>- Phase 3 - Backward && forward demanded info propagation and fusion
> across
> blocks.
>
Need update comment here.
>- Phase 6 - Propagate AVL between vsetvl instructions.
Need update comment here too.
> +/* Return true if the current VSETVL is dominated by preceding
On Wed, Aug 23, 2023 at 04:23:00PM -0400, Jason Merrill wrote:
> I'd be surprised if this would affect any real code, but I suppose so. In
> any case I'd like to fix this at the same time as the local statics, to
> avoid changing their mangled name twice.
Ok.
Running now into a problem with abi
On 22.08.23 15:37, Jakub Jelinek wrote:
On Sun, Jul 23, 2023 at 04:15:21PM -0600, Sandra Loosemore wrote:
[...]
In the Fortran front end, most of the semantic processing happens during
the translation phase, so the parse phase just collects the intervening
statements, checks them for errors,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=39589
Manuel López-Ibáñez changed:
What|Removed |Added
Keywords||patch
--- Comment #15 from Manuel
On Thu, Aug 24, 2023 at 05:47:09PM +0200, Richard Biener via Gcc-patches wrote:
> > Do you think that the pass is worthy of inclusion into upstream GCC? What
> > are
> > some things that I should change? Should I try to put the pass in different
> > places in passes.def?
>
> The most obvious
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=37
Bug ID: 37
Summary: Wrong code at -O2/3 since r12-1000-g6924b5e6bd3
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
On Thu, 24 Aug 2023 at 08:27, Thiago Jung Bauermann
wrote:
>
> Since commit e7a36e4715c7 "[PATCH] RISC-V: Support simplify (-1-x) for
> vector." these tests fail on aarch64-linux:
>
> === g++ tests ===
>
> Running g++:g++.target/aarch64/sve/acle/aarch64-sve-acle-asm.exp ...
>
> Am 24.08.2023 um 17:07 schrieb Filip Kastl :
>
> Hi,
>
> As a part of my bachelor thesis under the supervision of Honza (Jan Hubicka),
> I
> implemented a new PHI elimination algorithm into GCC. The algorithm is
> described in the following article:
>
> Braun, M., Buchwald, S., Hack, S.,
This patch fixes failing stack_save_restore_1/2 test cases.
After 6619b3d4c15c commit size of the frame was changed.
gcc/testsuite/ChangeLog:
* gcc.target/riscv/stack_save_restore_1.c: Update frame size
* gcc.target/riscv/stack_save_restore_2.c: Likewise.
--
With the best
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110973
Martin Jambor changed:
What|Removed |Added
CC||fkastl at suse dot cz,
1 - 100 of 267 matches
Mail list logo
