https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110660
--- Comment #1 from Richard Biener ---
The vectorizer itself could do the merging which means it could also more
accurately cost things.
Otherwise think about whether/how such a situation might arise from people
using RVV intrinsics - how are
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110659
Richard Biener changed:
What|Removed |Added
Target||x86_64-linux-gnu
--- Comment #8 from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110662
--- Comment #1 from CTC <19373742 at buaa dot edu.cn> ---
Created attachment 55540
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55540=edit
The compiler output
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110662
Bug ID: 110662
Summary: Segmentation fault with '-O3'
Product: gcc
Version: 11.4.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
From: Naveen H S
This patch adds lowering bit-field and opposite endian accesses pass.
The patch addresses many issues in:-
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=19466
2023-07-14 Andrew Pinski
Co-authored-by: Naveen H S
gcc/ChangeLog:
* Makefile.in (OBJS): Add
On 7/13/23 09:05, Manolis Tsamis wrote:
In this version I have made f-m-o able to also eliminate constant
moves in addition to the add constant instructions.
This increases the number of simplified/eliminated instructions and is
a good addition for RISC style ISAs where these are more common.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110652
--- Comment #4 from Kewen Lin ---
I can't reproduce this on ppc64le with both the default bootstrapping checking
option --enable-checking=yes,extra and the reported --enable-checking=release.
I'm going to test it on cfarm x86 machine.
If the
Hi all,
This patch is to add initial support for Lunar Lake, Arrow Lake and Arrow Lake
S for GCC.
This link of related information is listed below:
https://www.intel.com/content/www/us/en/develop/download/intel-architecture-instruction-set-extensions-programming-reference.html
This has been
On 7/13/23 20:41, Kito Cheng via Gcc-patches wrote:
Expanding without DONE or FAIL will leave the pattern as well, so this
patch is fine IMO, so this patch LGTM, but anyway I will test this and
commit if passed :)
THanks. I looked fine to me, but I wasn't going to have the time to
On 7/13/23 20:44, Palmer Dabbelt wrote:
On Thu, 13 Jul 2023 19:41:08 PDT (-0700), gcc-patches@gcc.gnu.org wrote:
Expanding without DONE or FAIL will leave the pattern as well, so this
patch is fine IMO, so this patch LGTM, but anyway I will test this and
commit if passed :)
Ah, thanks, I
From: Pan Li
This patch would like to support the basic floating-point dynamic
rounding modes for the RVV.
We implement the dynamic rounding mode by below steps.
1. Set entry to DYN and exit to DYN_EXIT.
2. Add one rtl variable into machine_function for backup/restore.
3. Backup frm value when
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110659
--- Comment #7 from Rich Townsend ---
(In reply to Andrew Pinski from comment #6)
> GCC 13 won't build with anything older than GCC 4.8.x as documented at
> https://gcc.gnu.org/install/prerequisites.html (which is right now for the
> trunk but
> The recent change in TImode parameter passing on x86_64 results in the FAIL
> of pr91681-1.c. The issue is that with the extra flexibility, the combine
> pass is
> now spoilt for choice between using either the
> *add3_doubleword_concat or the *add3_doubleword_zext
> patterns, when one operand
On Thu, 13 Jul 2023 19:41:08 PDT (-0700), gcc-patches@gcc.gnu.org wrote:
Expanding without DONE or FAIL will leave the pattern as well, so this
patch is fine IMO, so this patch LGTM, but anyway I will test this and
commit if passed :)
Ah, thanks, I guess I didn't know that. This is probably
Expanding without DONE or FAIL will leave the pattern as well, so this
patch is fine IMO, so this patch LGTM, but anyway I will test this and
commit if passed :)
On Fri, Jul 14, 2023 at 10:34 AM Palmer Dabbelt wrote:
>
> On Thu, 13 Jul 2023 19:02:05 PDT (-0700), li...@eswincomputing.com wrote:
>
On Thu, 13 Jul 2023 19:02:05 PDT (-0700), li...@eswincomputing.com wrote:
When generating the gen_and3 function based on the and3
template, it produces the expression emit_insn (gen_rtx_SET (operand0,
gen_rtx_AND (, operand1, operand2)));, which is identical to the
portion I removed in this
On Linux/x86_64,
450b05ce54d3f08c583c3b5341233ce0df99725b is the first bad commit commit
450b05ce54d3f08c583c3b5341233ce0df99725b
Author: Tobias Burnus
Date: Wed Jul 12 13:50:21 2023 +0200
libgomp: Use libnuma for OpenMP's partition=nearest allocation trait
caused
with GCC configured
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101469
Oleg Endo changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
Hi,
The attached patch fixes PR 101469.
Tested by the original reporter Rin Okuyama on NetBSD with GCC 10.5.
Applied to master, GCC 11, GCC 12, GCC 13 after 'make all' sanity check.
Cheers,
Oleg
gcc/ChangeLog:
PR target/101469
* config/sh/sh.md (peephole2): Handle case where
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101469
--- Comment #14 from CVS Commits ---
The releases/gcc-13 branch has been updated by Oleg Endo
:
https://gcc.gnu.org/g:ef4b6d29d9801c970bee1b3e8675b19ef5f61d2a
commit r13-7563-gef4b6d29d9801c970bee1b3e8675b19ef5f61d2a
Author: Oleg Endo
Date:
When generating the gen_and3 function based on the and3
template, it produces the expression emit_insn (gen_rtx_SET (operand0,
gen_rtx_AND (, operand1, operand2)));, which is identical to the
portion I removed in this patch. Therefore, the redundant portion can be
deleted.
Signed-off-by: Die Li
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110661
Bug ID: 110661
Summary: Weird handing for deleting a void* pointer
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Keywords: accepts-invalid
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110660
Bug ID: 110660
Summary: conditional length reduction optimization
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101469
--- Comment #13 from CVS Commits ---
The releases/gcc-12 branch has been updated by Oleg Endo
:
https://gcc.gnu.org/g:5f20f736c1144dd9f2ae2f99099b7f7b21a3ab4e
commit r12-9772-g5f20f736c1144dd9f2ae2f99099b7f7b21a3ab4e
Author: Oleg Endo
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101469
--- Comment #12 from CVS Commits ---
The releases/gcc-11 branch has been updated by Oleg Endo
:
https://gcc.gnu.org/g:75b8353e4b61566f7e8ac627204e2bcd6bfe60a6
commit r11-10909-g75b8353e4b61566f7e8ac627204e2bcd6bfe60a6
Author: Oleg Endo
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101469
--- Comment #11 from CVS Commits ---
The master branch has been updated by Oleg Endo :
https://gcc.gnu.org/g:4dbb3af1efe55174a714d15c2994cf2842ef8c28
commit r14-2511-g4dbb3af1efe55174a714d15c2994cf2842ef8c28
Author: Oleg Endo
Date: Fri Jul
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110653
--- Comment #8 from dave.anglin at bell dot net ---
On 2023-07-13 2:16 p.m., dave.anglin at bell dot net wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110653
>
> --- Comment #7 from dave.anglin at bell dot net ---
> On 2023-07-13 1:57
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110652
Kewen Lin changed:
What|Removed |Added
Last reconfirmed||2023-07-14
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54089
--- Comment #101 from Oleg Endo ---
(In reply to Alexander Klepikov from comment #100)
> Created attachment 55513 [details]
> Arithmetic right shift late expanding
>
> (In reply to Oleg Endo from comment #99)
> > Meanwhile, here's my iteration
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94094
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
Snapshot gcc-11-20230713 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/11-20230713/
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
Ok. Comments added:
in V2:
https://gcc.gnu.org/pipermail/gcc-patches/2023-July/624476.html
juzhe.zh...@rivai.ai
From: Robin Dapp
Date: 2023-07-13 23:25
To: juzhe.zhong; Kito Cheng
CC: rdapp.gcc; gcc-patches; jeffreyalaw; kito.cheng; palmer; palmer
Subject: Re: [PATCH] RISC-V: Enable
Add comments as Robin's suggestion in scatter_store_run-7.c
Enable COND_LEN_FMA auto-vectorization for floating-point FMA
auto-vectorization **NO** ffast-math.
Since the middle-end support has been approved and I will merge it after I
finished bootstrap && regression on X86.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97968
Andrew Pinski changed:
What|Removed |Added
Keywords||needs-bisection
Known to work|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97756
Andrew Pinski changed:
What|Removed |Added
CC||roger at nextmovesoftware dot
com
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110657
--- Comment #4 from Jose E. Marchesi ---
Looks like `combine' is generating paradoxical subregs of mems, which seem to
confuse LRA and these weird incorrect reloads end up being generated. The
easiest fix for this is to make the backend to use
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109112
--- Comment #7 from Jason Merrill ---
In an email thread Jakub wrote:
Only the simplest assumptions in [[assume(cond)]] where there clearly aren't
any
side-effects no risks of them are lowered to if (!cond) __builtin_unreachable
();
in the
This patch lets libstdc++ use new built-in trait __is_pointer.
libstdc++-v3/ChangeLog:
* include/bits/cpp_type_traits.h (__is_ptr): Use __is_pointer
built-in trait.
* include/std/type_traits (is_pointer): Likewise. Optimize its
implementation.
This patch implements built-in trait for std::is_pointer.
gcc/cp/ChangeLog:
* cp-trait.def: Define __is_pointer.
* constraint.cc (diagnose_trait_expr): Handle CPTK_IS_POINTER.
* semantics.cc (trait_expr_value): Likewise.
(finish_trait_expr): Likewise.
On 7/13/23 11:48, Patrick Palka wrote:
On Wed, 28 Jun 2023, Patrick Palka wrote:
On Wed, Jun 28, 2023 at 11:50 AM Jason Merrill wrote:
On 6/23/23 12:23, Patrick Palka wrote:
On Fri, 23 Jun 2023, Jason Merrill wrote:
On 6/21/23 13:19, Patrick Palka wrote:
When stepping through the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96050
--- Comment #1 from pkoning at gcc dot gnu.org ---
There certainly are some missing earlyclobbers in the MD file. Someone else
reported bad code from this and a patch to add the missing "&" fixed those.
Curious that it doesn't for your test
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103806
pkoning at gcc dot gnu.org changed:
What|Removed |Added
Status|WAITING |ASSIGNED
--- Comment #3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103801
pkoning at gcc dot gnu.org changed:
What|Removed |Added
Status|WAITING |ASSIGNED
On Thu, Jul 06, 2023 at 06:56:21PM +, Qing Zhao wrote:
> Hi, Kees,
>
> I have updated my V1 patch with the following changes:
> A. changed the name to "counted_by"
> B. changed the argument from a string to an identifier
> C. updated the documentation and testing cases accordingly.
Sounds
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105834
Andrew Pinski changed:
What|Removed |Added
Keywords||needs-bisection
Known to work|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96945
Andrew Pinski changed:
What|Removed |Added
Component|c++ |tree-optimization
Last reconfirmed|
Ping.
On 6/30/23 2:26 PM, Pat Haugen via Gcc-patches wrote:
Updated from prior version to address latest review comment (simplify
umod3).
Disable generation of scalar modulo instructions.
It was recently discovered that the scalar modulo instructions can suffer
noticeable performance issues
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103801
pkoning at gcc dot gnu.org changed:
What|Removed |Added
CC||pkoning at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107841
pkoning at gcc dot gnu.org changed:
What|Removed |Added
Resolution|--- |FIXED
> On Jul 13, 2023, at 12:47 PM, Mikael Pettersson wrote:
>
> If the stack frame only contains an alloca area, then
> pdp11_expand_epilogue fails to deallocate it, resulting
> in callee-saved registers and the return address being
> restored from the wrong stack slots. Fixed by adding
> ||
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107841
--- Comment #3 from CVS Commits ---
The master branch has been updated by Paul Koning :
https://gcc.gnu.org/g:8f1a26ee259f72e42405b9c5f2b161042ec4014b
commit r14-2509-g8f1a26ee259f72e42405b9c5f2b161042ec4014b
Author: Mikael Pettersson
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96533
Patrick Palka changed:
What|Removed |Added
Status|NEW |RESOLVED
Target Milestone|---
On Thu, Jul 13, 2023 at 2:22 AM Jonathan Wakely wrote:
>
> On Wed, 12 Jul 2023 at 21:42, Ken Matsui wrote:
> >
> > On Wed, Jul 12, 2023 at 3:01 AM Jonathan Wakely wrote:
> > >
> > > On Mon, 10 Jul 2023 at 06:51, Ken Matsui via Libstdc++
> > > wrote:
> > > >
> > > > Hi,
> > > >
> > > > Here is
Hi Mikael,
Am 11.07.23 um 12:32 schrieb Mikael Morin via Gcc-patches:
Hello,
this is a followup to Harald's recent work [1] on the evaluation order
of arguments, when one of them is passed to an intent(out) allocatable
dummy and is deallocated before the call.
This extends Harald's fix to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110659
--- Comment #6 from Andrew Pinski ---
GCC 13 won't build with anything older than GCC 4.8.x as documented at
https://gcc.gnu.org/install/prerequisites.html (which is right now for the
trunk but that requirement has not changed yet).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92178
Mikael Morin changed:
What|Removed |Added
CC||mikael at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110659
--- Comment #5 from Rich Townsend ---
(In reply to Andrew Pinski from comment #2)
> What compiler did you start with?
> That is what is the output of `x86_64-pc-linux-gnu-g++ -v` ?
[user@60947d0cbd04 ~]$ x86_64-pc-linux-gnu-g++ -v
bash:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110618
Mikael Morin changed:
What|Removed |Added
Last reconfirmed||2023-07-13
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110659
--- Comment #4 from Rich Townsend ---
Someone else seems to have the same problem:
https://stackoverflow.com/questions/76375244/how-can-i-resolve-a-ld-eh-frame-hdr-refers-to-overlapping-fdes-error-during
...although there is no fix suggested.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110659
Andrew Pinski changed:
What|Removed |Added
Last reconfirmed||2023-07-13
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110659
--- Comment #2 from Andrew Pinski ---
What compiler did you start with?
That is what is the output of `x86_64-pc-linux-gnu-g++ -v` ?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110659
--- Comment #1 from Rich Townsend ---
I should add that this is on CentOS 5.11, running inside a Docker container.
This ships with a very old binutils, so before trying to compile gcc I
installed binutils 2.40 (built from source with
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106050
--- Comment #8 from CVS Commits ---
The master branch has been updated by Mikael Morin :
https://gcc.gnu.org/g:616a101848bfd5b61ffdd87ae9b1153139d916ca
commit r14-2507-g616a101848bfd5b61ffdd87ae9b1153139d916ca
Author: Mikael Morin
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110659
Bug ID: 110659
Summary: Error from linker: .eh_frame_hdr refers to overlapping
FDEs
Product: gcc
Version: 13.1.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110624
Iain Sandoe changed:
What|Removed |Added
Resolution|--- |FIXED
Status|WAITING
tested on i688, x86_64 Darwin versions with/without support for the
platform_version flag. Checked by Rainer on macOS14. Pushed to trunk
thanks,
Iain
--- 8< ---
Later versions of the static linker support a more flexible flag to
describe the OS, OS version and SDK used to build the code. This
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110624
--- Comment #7 from CVS Commits ---
The master branch has been updated by Iain D Sandoe :
https://gcc.gnu.org/g:032b5da1fc781bd3c23d9caa72fb09439e7f6f3a
commit r14-2506-g032b5da1fc781bd3c23d9caa72fb09439e7f6f3a
Author: Iain Sandoe
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96533
Patrick Palka changed:
What|Removed |Added
Known to work||12.1.0, 13.1.0
Known to fail|
> -Original Message-
> From: Richard Biener
> Sent: Thursday, July 13, 2023 6:31 PM
> To: Tamar Christina
> Cc: gcc-patches@gcc.gnu.org; nd ; j...@ventanamicro.com
> Subject: Re: [PATCH 12/19]middle-end: implement loop peeling and IV
> updates for early break.
>
> On Wed, 28 Jun 2023,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110619
Patrick Palka changed:
What|Removed |Added
CC||natattak at gmail dot com,
On Fri, May 26, 2023 at 09:47:10PM -0400, Jason Merrill wrote:
> On 5/26/23 19:18, Marek Polacek wrote:
> > Since r8-509, we'll no longer create a static temporary var for
> > the initializer '{ 1, 2 }' for num in the attached test because
> > the code in finish_compound_literal is now guarded by
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110652
Sergei Trofimovich changed:
What|Removed |Added
CC||linkw at gcc dot gnu.org
---
On 7/13/23 11:46, Paul Koning via Gcc-patches wrote:
On Jul 13, 2023, at 12:47 PM, Mikael Pettersson wrote:
If the stack frame only contains an alloca area, then
pdp11_expand_epilogue fails to deallocate it, resulting
in callee-saved registers and the return address being
restored from
Bootstrapped and regtested on x86_64-pc-linux-gnu, does this look OK for
trunk?
-- >8 --
Here the call A().f() is represented as a COMPOUND_EXPR whose first
operand is the otherwise unused object argument A() and second operand
is the call result (both are TARGET_EXPRs). Within the return
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93719
--- Comment #1 from pkoning at gcc dot gnu.org ---
This works with -mlra, so given the deprecation of old reload the right answer
seems to be to close this as fixed.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106379
Andrew Pinski changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106570
Andrew Pinski changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101240
--- Comment #5 from Andrew Pinski ---
here is a better testcase:
```
int test_array(unsigned ()[3]) {
int t = (a[0]+a[1]+a[2]);
ALWAYS_TRUE(a[0] < a[1] && a[1] < a[2]);
return (a[0] < a[2])+t;
}
```
(just to make sure VRP is only dealing
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110658
Bug ID: 110658
Summary: MINVAL/MAXVAL and deferred-length character arrays
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
On Thu, Jul 13, 2023 at 7:10 PM Roger Sayle wrote:
>
>
> This patch resolves PR target/110588 to catch another case in combine
> where the i386 backend should be generating a btl instruction. This adds
> another define_insn_and_split to recognize the RTL representation for this
> case.
>
> I
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110653
--- Comment #7 from dave.anglin at bell dot net ---
On 2023-07-13 1:57 p.m., dave.anglin at bell dot net wrote:
> ./hppa64-hp-hpux11.11/libstdc++-v3/include/bits/basic_string.h:4161:36: error:
> 'strtold' is not a member of 'std'; did you mean
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108953
Andrew Pinski changed:
What|Removed |Added
CC||jengelh at inai dot de
--- Comment #5
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103733
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |DUPLICATE
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59172
pkoning at gcc dot gnu.org changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Rainer Orth writes:
> When trying to bootstrap current trunk on macOS 14.0 beta 3 with Xcode
> 15 beta 4, the build failed running mklink in stage 2:
>
> unset CC ; m2/boot-bin/mklink -s --langc++ --exit --name m2/mc-boot/main.cc
> /vol/gcc/src/hg/master/darwin/gcc/m2/init/mcinit
> dyld[55825]:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59178
pkoning at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102989
Jakub Jelinek changed:
What|Removed |Added
Attachment #55530|0 |1
is obsolete|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110653
--- Comment #6 from dave.anglin at bell dot net ---
On 2023-07-13 1:09 p.m., redi at gcc dot gnu.org wrote:
> I'm testing this, which should define std::stof and std::stold for hpux11.11:
>
> --- a/libstdc++-v3/include/bits/basic_string.h
> +++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107841
pkoning at gcc dot gnu.org changed:
What|Removed |Added
Last reconfirmed||2023-07-13
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110206
--- Comment #15 from Uroš Bizjak ---
Created attachment 55537
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55537=edit
Proposed patch.
v2 patch in testing.
This version prevents emission of invalid REG_EQUAL note in
> On Jul 13, 2023, at 12:47 PM, Mikael Pettersson wrote:
>
> If the stack frame only contains an alloca area, then
> pdp11_expand_epilogue fails to deallocate it, resulting
> in callee-saved registers and the return address being
> restored from the wrong stack slots. Fixed by adding
> ||
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110288
--- Comment #7 from anlauf at gcc dot gnu.org ---
The fix for FINDLOC also fixes the same regression for MINLOC, MAXLOC.
There is another issue for MINVAL and MAXVAL that exists already in
10-branch, thus not a regression. I get at runtime:
On Wed, 28 Jun 2023, Tamar Christina wrote:
> Hi All,
>
> This patch updates the peeling code to maintain LCSSA during peeling.
> The rewrite also naturally takes into account multiple exits and so it didn't
> make sense to split them off.
>
> For the purposes of peeling the only change for
This patch resolves PR target/110588 to catch another case in combine
where the i386 backend should be generating a btl instruction. This adds
another define_insn_and_split to recognize the RTL representation for this
case.
I also noticed that two related define_insn_and_split weren't using the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78710
Jonathan Wakely changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110653
--- Comment #5 from Jonathan Wakely ---
(In reply to dave.anglin from comment #3)
> On 2023-07-13 9:46 a.m., redi at gcc dot gnu.org wrote:
> > Dave, does this patch work for hppa64-hp-hpux11.11 ?
> Yes.
Great - pushed to trunk.
> On hpux,
Tested powerpc64le-linux. Pushed to trunk.
-- >8 --
std::stoi, std::stol, std::stoul, and std::stod only depend on C89
functions, so don't need to be guarded by _GLIBCXX_USE_C99_STDLIB
std::stoll and std::stoull don't need C99 strtoll and strtoull if
sizeof(long) == sizeof(long long).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110653
--- Comment #4 from CVS Commits ---
The master branch has been updated by Jonathan Wakely :
https://gcc.gnu.org/g:a1d12752f8d45df5d7962cef6e2a87585002e982
commit r14-2504-ga1d12752f8d45df5d7962cef6e2a87585002e982
Author: Jonathan Wakely
On 7/13/23 08:20, Manolis Tsamis wrote:
I have sent a V3 which contains a number of fixes and improvements:
https://gcc.gnu.org/pipermail/gcc-patches/2023-July/624439.html
I tested the new version rebased on master and the m68k issue did not reproduce.
I don't know what exactly fixed it; do
If the stack frame only contains an alloca area, then
pdp11_expand_epilogue fails to deallocate it, resulting
in callee-saved registers and the return address being
restored from the wrong stack slots. Fixed by adding
|| cfun->calls_alloca to the condition for deallocating
the frame.
Tested with
1 - 100 of 250 matches
Mail list logo
