On 9/29/23 16:53, Jivan Hakobyan wrote:
After f088b768d01a commit riscv_sched_variable_issue function requires
that all insns should have a type attribute.
When I sent my previous patch there was no such limitation.
Currently, I have regressions on my tests. This patch fixes them.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111566
--- Comment #5 from Jorn Wolfgang Rennecke ---
I had a look at riscv_legitimize_move. It doesn't seem to suffer from quite
the same problem as legitimize_move does, but it could if another problem was
fixed: riscv_legitimize_move changes the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111566
--- Comment #4 from Jorn Wolfgang Rennecke ---
Also, the GET_MODE_BITSIZE (mode).to_constant () <= MAX_BITS_PER_WORD
in the *mov_mem_to_mem splitter can generate unaligned accesses, yet it
is not guarded by a check that the target supports
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111566
--- Comment #3 from Jorn Wolfgang Rennecke ---
riscv-v.cc:legitimize_move has:
if (MEM_P (dest) && !REG_P (src))
src = force_reg (mode, src);
return false;
since src is passed by value, this is pointless. The
Sent from my iPhone set t
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111645
Bug ID: 111645
Summary: Intrinsics vec_sldb /vec_srdb fail with __vector
unsigned __int128
Product: gcc
Version: 13.2.1
Status: UNCONFIRMED
Severity: normal
After f088b768d01a commit riscv_sched_variable_issue function requires
that all insns should have a type attribute.
When I sent my previous patch there was no such limitation.
Currently, I have regressions on my tests. This patch fixes them.
gcc/ChangeLog:
* config/riscv/bitmanip.md
Snapshot gcc-12-20230929 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/12-20230929/
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
So this ends up looking a lot like the bits that I had to revert several
weeks ago :-)
The core issue we have is given an INSN the generic code will cost the
SET_SRC and SET_DEST and sum them. But that's far from ideal on a RISC
target.
For a register destination, the cost can be
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111566
Jorn Wolfgang Rennecke changed:
What|Removed |Added
CC||amylaar at gcc dot gnu.org
On 9/29/23 14:59, Jeff Law wrote:
On 9/29/23 15:37, Patrick O'Neill wrote:
Resolves this error on rv32gcv:
cc1: error: ABI requires '-march=rv32'
compiler exited with status 1
FAIL: gcc.target/riscv/rvv/vsetvl/wredsum_vlmax.c -O0 (test for
excess errors)
Tested for regressions using
On 9/29/23 15:11, Roger Sayle wrote:
Hi Claudiu,
The patch looks sane. Have you run dejagnu test suite?
I've not yet managed to set up an emulator or compile the entire toolchain,
so my dejagnu results are only useful for catching (serious) problems in the
compile only tests:
On 9/29/23 15:37, Patrick O'Neill wrote:
Resolves this error on rv32gcv:
cc1: error: ABI requires '-march=rv32'
compiler exited with status 1
FAIL: gcc.target/riscv/rvv/vsetvl/wredsum_vlmax.c -O0 (test for excess
errors)
Tested for regressions using glibc rv32gcv/rv64gcv multilib on
Resolves this error on rv32gcv:
cc1: error: ABI requires '-march=rv32'
compiler exited with status 1
FAIL: gcc.target/riscv/rvv/vsetvl/wredsum_vlmax.c -O0 (test for excess
errors)
Tested for regressions using glibc rv32gcv/rv64gcv multilib on
r14-4339-geaa41a6dc12.
gcc/testsuite/ChangeLog:
On 9/29/23 12:05, Jeff Law wrote:
On 9/12/23 12:54, Patrick O'Neill wrote:
This testcase causes lots of false-positives for machine description
files.
contrib/ChangeLog:
* check_GNU_style_lib.py: Skip machine description file bracket
linting.
OK. We probably need a completely
Hi Claudiu,
> The patch looks sane. Have you run dejagnu test suite?
I've not yet managed to set up an emulator or compile the entire toolchain,
so my dejagnu results are only useful for catching (serious) problems in the
compile only tests:
=== gcc Summary ===
# of expected
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111644
Bug ID: 111644
Summary: [13 regression] many failures after
r13-7923-gd9b3269bdccac2
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
On 9/28/23 03:46, Maciej W. Rozycki wrote:
On Wed, 27 Sep 2023, Jeff Law wrote:
IMO this is one of those places where we should just be as normal as
possible. So if the other big ports allow system headers then we should,
otherwise we should move everyone over to testing in some way we'll
On 8/23/23 22:53, Li, Pan2 wrote:
Thanks Jeff.
That implies a save/restore pair around the call (possibly optimized so
that we minimize the number of save/restores). I would have expected
x86 to already be doing this. But maybe there's some ABI thing around
mmx vs x86 state that allows it
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111642
--- Comment #1 from Sergei Trofimovich ---
Looks like this code is all under `#if CHECKING_P` of sorts. A few more
possibly affected entries:
```
$ git grep -P 'poly_int64 \(\d+, \d+\)'
gcc/config/riscv/riscv-selftests.cc:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111643
Marc Glisse changed:
What|Removed |Added
CC||glisse at gcc dot gnu.org
--- Comment #2
On 8/25/23 06:44, Li, Pan2 wrote:
Hi Jeff,
You might also peek at the RTL gcse/pre code which is also LCM based and
has the same class of problems.
I found a similar approach to take care of this in gcse.cc/pre_edge_insert with
some comments as below.
/* We can't insert anything on
On 9/5/23 01:12, Andrew Pinski wrote:
On Mon, Sep 4, 2023 at 11:06 PM Jeff Law via Gcc-patches
wrote:
On 9/1/23 11:30, Andrew Pinski via Gcc-patches wrote:
So it turns out there was a simplier way of starting to
improve VRP to start to fix PR 110131, PR 108360, and PR 108397.
That was
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111427
--- Comment #3 from Vladimir Makarov ---
Sorry for the inconvenience caused by the patch. I reverted this patch
yesterday.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111643
Andrew Pinski changed:
What|Removed |Added
Component|c |ipa
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111643
Bug ID: 111643
Summary: __attribute__((flatten)) with -O1 runs out of memory
(killed cc1)
Product: gcc
Version: 13.2.0
Status: UNCONFIRMED
Severity: normal
On 9/5/23 01:46, Andrew Pinski wrote:
On Tue, Sep 5, 2023 at 12:09 AM Jeff Law via Gcc-patches
wrote:
On 9/1/23 20:32, Andrew Pinski via Gcc-patches wrote:
This turns out to be a latent bug in ssa_name_has_boolean_range
where it would return true for all boolean types but all of the
On Fri, Sep 29, 2023 at 2:09 PM Michael Meissner
wrote:
> When I first implemented COPYSIGN support in the power7 days, we did not
> have a
> copysign RTL insn, so I had to use UNSPEC to represent the copysign
> instruction. This patch removes those UNSPECs, and it uses the native RTL
>
On 9/12/23 13:09, Jivan Hakobyan via Gcc-patches wrote:
In the case when we have C code like this
int foo (int a) {
return 100 & ~a;
}
GCC generates the following instruction sequence
foo:
not a0,a0
andia0,a0,100
ret
This patch replaces that with this
On 9/12/23 03:18, Feng Wang wrote:
New patch add some comments and update docs for this new usage.
---
Accoring to Kito's advice, using "MASK(name) Var(other_flag_name)"
to generate MASK and TARGET MACRO automatically.
This patch improve the MACRO generation of MASK_* and TARGET_*.
Due to the
On 9/12/23 04:13, Manolis Tsamis wrote:
+
+/* Get the single reaching definition of an instruction inside a BB.
+ The definition is desired for REG used in INSN.
+ Return the definition insn or NULL if there's no definition with
+ the desired criteria. */
+static rtx_insn*
Hi,
This patch implements pex_unix_exec_child using posix_spawn when
available.
This should especially benefit recent macOS (where vfork just calls
fork), but should have equivalent or faster performance on all
platforms.
In addition, the implementation is substantially simpler than the
rted LTO compression algorithms: zlib
gcc version 14.0.0 20230929 (experimental) (GCC)
On 9/12/23 12:54, Patrick O'Neill wrote:
This testcase causes lots of false-positives for machine description files.
contrib/ChangeLog:
* check_GNU_style_lib.py: Skip machine description file bracket linting.
OK. We probably need a completely separate checker for for .md files.
On 8/10/23 07:04, Stefan Schulze Frielinghaus via Gcc-patches wrote:
In the former fix in commit 41ef5a34161356817807be3a2e51fbdbe575ae85 I
completely missed the fact that the normal form of a generated constant for a
mode with fewer bits than in HOST_WIDE_INT is a sign extended version of
On 9/19/23 10:06, Stefan Schulze Frielinghaus wrote:
Since this patch is sitting in the queue for quite some time and (more
importantly?) solves a bootstrap problem let me reiterate:
While writing the initial commit 7cdd0860949c6c3232e6cff1d7ca37bb5234074c
and the subsequent (potential) fix
On 9/29/23 12:05, Kito Cheng wrote:
Hi Jeff:
Could you take a look for this? RISC-V part is ok to me.
Thanks :)
Yea, I've got two things on my list to review from a doc standpoint.
This is one of 'em.
jeff
When I first implemented COPYSIGN support in the power7 days, we did not have a
copysign RTL insn, so I had to use UNSPEC to represent the copysign
instruction. This patch removes those UNSPECs, and it uses the native RTL
copysign insn.
I have tested this on both big endian and little endian
Hi Jeff:
Could you take a look for this? RISC-V part is ok to me.
Thanks :)
Feng Wang 於 2023年9月12日 週二 17:18 寫道：
> New patch add some comments and update docs for this new usage.
> ---
> Accoring to Kito's advice, using "MASK(name) Var(other_flag_name)"
> to generate MASK and TARGET MACRO
Hi Roger,
The patch looks sane. Have you run dejagnu test suite?
Thanks,
Claudiu
-Original Message-
From: Roger Sayle
Sent: Friday, September 29, 2023 6:54 PM
To: gcc-patches@gcc.gnu.org
Cc: Claudiu Zissulescu
Subject: [ARC PATCH] Use rlc r0,0 to implement scc_ltu (i.e. carry_flag ?
On 27 September 2023 06:46:29 CEST, Bernhard Reutner-Fischer
wrote:
>On 27 September 2023 06:43:24 CEST, Jakub Jelinek wrote:
>>Hi!
>>
>>While looking into vec.h, I've noticed we still have a workaround for
>>GCC 4.1-4.3 bugs.
>
>
>This is https://gcc.gnu.org/PR105656
>thanks,
Mere cosmetics,
On 9/19/23 02:46, Jin Ma wrote:
This patch adds the 'Zfbfmin' extension for riscv, which is based on spec of
bfloat16:
https://github.com/riscv/riscv-bfloat16/commit/5578e34e15a44e9ad13246072a29f51274b4d999
The 'Zfbfmin' extension of binutils-gdb (REVIEW ONLY):
On 9/19/23 02:44, Jin Ma wrote:
gcc/ChangeLog:
* config/riscv/iterators.md (HFBF): New.
* config/riscv/riscv-builtins.cc (riscv_init_builtin_types):
Initialize data type_Bfloat16.
* config/riscv/riscv-modes.def (FLOAT_MODE): New.
(ADJUST_FLOAT_FORMAT):
Thanks Jeff, pushed as 94e68ce96c285e479736851f1ad8cc87c8c3ff0c
FX
On 9/20/23 07:53, FX Coudert wrote:
ping**2
Hi,
This was a painful one to fix, because I hate regexps, especially when they are
quoted. On darwin, we have this failure:
FAIL: gcc.dg/debug/dwarf2/inline4.c scan-assembler
Arsen Arsenović wrote:
> Do you like the following?
>
> @@ -486,7 +486,7 @@ found in a subdirectory of your GCC sources
> will be built together with GCC, unless present in the system (either in
> libc or as a stand-alone library).
>
> -The in-tree configuration requires GNU gettext v0.22.
>
On Fri, 29 Sept 2023 at 17:29, Nathaniel Shead
wrote:
>
> On Fri, Sep 29, 2023 at 04:06:33PM +0100, Jonathan Wakely wrote:
> > On Fri, 29 Sept 2023 at 10:32, Jonathan Wakely wrote:
> > > > Thanks for the comments, here's an updated version of the patch.
> > > > Bootstrapped and regtested on
On Fri, Sep 29, 2023 at 04:06:33PM +0100, Jonathan Wakely wrote:
> On Fri, 29 Sept 2023 at 10:32, Jonathan Wakely wrote:
> > > Thanks for the comments, here's an updated version of the patch.
> > > Bootstrapped and regtested on x86_64-pc-linux-gnu.
> >
> > Great, I'll get this committed today -
Bruno Haible writes:
> Arsen Arsenović wrote:
>> -+The in-tree configuration requires GNU gettext v0.22.
>
> Can you change this to "... requires GNU gettext version 0.22 or newer.",
> please?
> I wouldn't like to give the impression that a particular release (0.22) is the
> only one that
Since 2005, it was assumed in the Linux kernel that all PA 2.0 processors
supported the ldcw cacheable hint and that natural alignment could be used
for ldcw,co. However, I recently fired up an old A500 machine with PA8600
processors and found that 16-byte alignment was needed for ldcw,co on it.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111636
Andrew Pinski changed:
What|Removed |Added
Resolution|FIXED |INVALID
--- Comment #4 from Andrew
This patch teaches the ARC backend that the contents of the carry flag
can be placed in an integer register conveniently using the "rlc rX,0"
instruction, which is a rotate-left-through-carry using zero as a source.
This is a convenient special case for the LTU form of the scc pattern.
unsigned
Hi, I have recently been working on issues related to the changing
values of global variables. That is, I was trying to develop a gimple
pass, which needs to check whether the value of a global variable is
modified in the a function or some blocks.
Some of the more tricky cases are as follows:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111589
--- Comment #3 from Jonathan Wakely ---
(In reply to Jonathan Wakely from comment #2)
> The interesting question is whether all of these can be relaxed or if we
> need to stop using __atomic_add_dispatch for shared_ptr copies:
>
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111640
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |INVALID
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111640
--- Comment #1 from Andrew Pinski ---
Induction variable (int) var_45_lsm.67_240 + -2147483643 + -2147483643 *
iteration does not wrap in statement _153 = var_45_lsm.67_226 + -2147483643;
in loop 1.
Statement _153 = var_45_lsm.67_226 +
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111641
--- Comment #1 from Jonathan Wakely ---
This fails the same way on 32-bit arm. Presumably some difference in
libbacktrace support.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110900
Jonathan Wakely changed:
What|Removed |Added
Target Milestone|--- |12.4
--- Comment #8 from Jonathan
On Fri, 29 Sept 2023 at 10:32, Jonathan Wakely wrote:
> > Thanks for the comments, here's an updated version of the patch.
> > Bootstrapped and regtested on x86_64-pc-linux-gnu.
>
> Great, I'll get this committed today - thanks!
That's done now.
> >
> > I'll note that there are some existing
On Thu, 28 Sept 2023 at 20:39, Dimitrij Mijoski via Libstdc++
wrote:
>
> This patch fixes the handling of surrogate code points in all standard
> facets for transcoding Unicode that are based on std::codecvt. Surrogate
> code points should always be treated as error. On the other hand
> surrogate
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108976
--- Comment #8 from CVS Commits ---
The master branch has been updated by Jonathan Wakely :
https://gcc.gnu.org/g:a8b9c32da787ea0bfbfc9118ac816fa7be4b1bc8
commit r14-4335-ga8b9c32da787ea0bfbfc9118ac816fa7be4b1bc8
Author: Dimitrij Mijoski
On 9/26/23 18:50, Tamar Christina wrote:
Hi All,
For targets that allow conversion between int and float modes this adds a new
optimization transforming fneg (fabs (x)) into x | (1 << signbit(x)). Such
sequences are common in scientific code working with gradients.
The transformed
On 9/29/23 02:19, Paul Iannetta wrote:
On Tue, Sep 26, 2023 at 08:29:11AM -0600, Jeff Law wrote:
On 9/25/23 03:55, Paul Iannetta wrote:
On Mon, Sep 18, 2023 at 08:39:34AM +0200, Paul Iannetta wrote:
On Thu, Sep 14, 2023 at 04:24:33PM +0200, Paul Iannetta wrote:
Hi,
This is a small
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111641
Bug ID: 111641
Summary: FAIL: 19_diagnostics/stacktrace/current.cc
-std=gnu++23 execution test
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111637
--- Comment #1 from Jakub Jelinek ---
Untested fix in https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111625#c2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111625
--- Comment #2 from Jakub Jelinek ---
Created attachment 56016
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56016=edit
gcc14-pr111625.patch
Untested fix.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111640
Bug ID: 111640
Summary: Missed optimization of Loop Unswitch (Simple loops)
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111637
Jakub Jelinek changed:
What|Removed |Added
Ever confirmed|0 |1
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111625
Jakub Jelinek changed:
What|Removed |Added
Version|unknown |14.0
Assignee|unassigned at
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111522
--- Comment #11 from Mathieu Malaterre ---
Here is a dead simple reduced version:
```
% cat pr111522.cc
#include
#include
#pragma GCC push_options
#pragma GCC target "cpu=power10"
float BitCast(int in) {
float out;
memcpy(, ,
On Fri, 29 Sept 2023 at 15:07, Jonathan Wakely wrote:
>
> On Tue, 6 Dec 2016 at 17:59, Jonathan Wakely wrote:
> > >Subject: [PATCH 3/3] Enable libstdc++ compilation in AVR targets
> > >
> > >Enable libstdc++ compilation in AVR targets with AVR-Libc. Most
> > >floating point math functions are
On Tue, 6 Dec 2016 at 17:59, Jonathan Wakely wrote:
> >Subject: [PATCH 3/3] Enable libstdc++ compilation in AVR targets
> >
> >Enable libstdc++ compilation in AVR targets with AVR-Libc. Most
> >floating point math functions are already defined in AVR-Libc, so
> >defines are in place to avoid
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111639
Jonathan Wakely changed:
What|Removed |Added
Ever confirmed|0 |1
Blocks|
On 9/27/23 17:21, Vineet Gupta wrote:
On 9/27/23 13:14, Jeff Law wrote:
It would help to describe how these patterns were under specified so
that folks don't continue to make the same mistake as new tests get
added.
dg-final scan-assembler, scan-assembler-not, and scan-assembler-times
On 9/29/23 04:40, Roger Sayle wrote:
I agree that this looks dubious. Normally, if the middle-end/optimizers
wish to reuse a SUBREG in a context where the flags are not valid, it
should create a new one with the desired flags, rather than "mutate"
an existing (and possibly shared) RTX.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111639
Bug ID: 111639
Summary: HAVE_ACOSF etc. are wrong on avr
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
Hello All:
This patch add new pass to replace contiguous addresses vector load lxv with
mma instruction
lxvp.
Bootstrapped and regtested with powepc64-linux-gnu.
Thanks & Regards
Ajit
rs6000: Add new pass for replacement of contiguous lxv with lxvp
New pass to replace contiguous addresses
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111638
Bug ID: 111638
Summary: GLIBCXX_MAYBE_UNDERSCORED_FUNCS autoconf macro doesn't
work
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Hi Paul,
thanks. Commit to trunk as a680274616ec6b26ccfdcee400ed7f54e341d40c
and backported to gcc-13 as d9b3269bdccac2db9200303494c4e82f2aeb7bbc
Thanks for the fast review.
Regards,
Andre
On Fri, 29 Sep 2023 13:38:57 +0100
Paul Richard Thomas wrote:
> Hi Andre,
>
> Yes indeed - it's
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=37336
--- Comment #35 from CVS Commits ---
The releases/gcc-13 branch has been updated by Andre Vehreschild
:
https://gcc.gnu.org/g:d9b3269bdccac2db9200303494c4e82f2aeb7bbc
commit r13-7923-gd9b3269bdccac2db9200303494c4e82f2aeb7bbc
Author: Andre
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=37336
--- Comment #34 from CVS Commits ---
The master branch has been updated by Andre Vehreschild :
https://gcc.gnu.org/g:a680274616ec6b26ccfdcee400ed7f54e341d40c
commit r14-4331-ga680274616ec6b26ccfdcee400ed7f54e341d40c
Author: Andre Vehreschild
On Fri, 29 Sep 2023, Jakub Jelinek wrote:
> Hi!
>
> As reported by Jonathan on IRC, my vec.h patch broke build with GCC 4.8.x
> or 4.9.x as system compiler, e.g. on CFarm.
> The problem is that while all of
> std::is_trivially_{destructible,copyable,default_constructible} traits
> are in C++,
Hi Andre,
Yes indeed - it's fine for trunk and, I would suggest, 13-branch.
Cheers
Paul
On Fri, 29 Sept 2023 at 11:01, Andre Vehreschild wrote:
>
> Hi Paul,
>
> thanks for the quick review. I've added a testcase with a module and a
> finalizer in the derived type. This also is no problem.
>
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=31
--- Comment #1 from Richard Biener ---
There's also
if (memory_access_type == VMAT_GATHER_SCATTER && gs_info.decl)
{
vect_build_gather_load_calls (vinfo, stmt_info, gsi, vec_stmt, _info,
mask,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=21
Wilco changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=21
--- Comment #4 from CVS Commits ---
The releases/gcc-12 branch has been updated by Wilco Dijkstra
:
https://gcc.gnu.org/g:bc1e385488001b0bd1a9b9c55b09ce987c31d353
commit r12-9898-gbc1e385488001b0bd1a9b9c55b09ce987c31d353
Author: Wilco
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=21
--- Comment #3 from CVS Commits ---
The releases/gcc-13 branch has been updated by Wilco Dijkstra
:
https://gcc.gnu.org/g:c534a9b198caa3807bcc592a3c5bac3f971417f7
commit r13-7921-gc534a9b198caa3807bcc592a3c5bac3f971417f7
Author: Wilco
On 9/28/23 21:49, Vineet Gupta wrote:
On 9/28/23 20:17, Jeff Law wrote:
I can bootstrap & regression test alpha using QEMU user mode
emulation. So we might be able to trigger something that way. It'll
take some time, but might prove fruitful.
That would be awesome. It's not like this
On 9/29/23 04:37, Jakub Jelinek wrote:
On Thu, Sep 28, 2023 at 11:53:53AM -0400, Aldy Hernandez wrote:
ipa_bits is even worse, because unlike niter analysis, I think it is very
much desirable to support IPA VRP of all supported _BitInt sizes. Shall
we perhaps use trailing_wide_int storage
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111636
KL changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
Arsen Arsenović wrote:
> -+The in-tree configuration requires GNU gettext v0.22.
Can you change this to "... requires GNU gettext version 0.22 or newer.",
please?
I wouldn't like to give the impression that a particular release (0.22) is the
only one that works.
Also, some people may understand
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110158
--- Comment #7 from Jonathan Wakely ---
That bug in comment 6 has already been fixed in gcc-12.3, by the last patch for
PR 103295.
The one in comment 4 is different, and will be fixed by Nathaniel's latest
patch:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110900
Jonathan Wakely changed:
What|Removed |Added
Resolution|DUPLICATE |---
Status|RESOLVED
On Fri, Sep 29, 2023 at 11:30:06AM +0100, Richard Sandiford wrote:
> Yeah, think I agree with this. widest_int really combined two things:
>
> (a) a way of storing any integer IL value without loss of precision
>
> (b) a way of attaching sign information
>
> Arithmetic on widest_int is
Applied to master. Thanks!
--Philipp.
On Fri, 29 Sept 2023 at 12:34, Richard Sandiford
wrote:
>
> Manos Anagnostakis writes:
> > Improves on: 834fc2bf
> >
> > This improves the code structure of the ldp-stp policies
> > patch introduced in 834fc2bf
> >
> > Bootstrapped and regtested on
Hi!
As reported by Jonathan on IRC, my vec.h patch broke build with GCC 4.8.x
or 4.9.x as system compiler, e.g. on CFarm.
The problem is that while all of
std::is_trivially_{destructible,copyable,default_constructible} traits
are in C++, only std::is_trivially_destructible has been implemented in
I agree that this looks dubious. Normally, if the middle-end/optimizers
wish to reuse a SUBREG in a context where the flags are not valid, it
should create a new one with the desired flags, rather than "mutate"
an existing (and possibly shared) RTX.
I wonder if creating a new SUBREG here also
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111637
Bug ID: 111637
Summary: ICE while building gcc.dg/bitint-8.c with
-fsanitize=signed-integer-overflow
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity:
Manos Anagnostakis writes:
> Improves on: 834fc2bf
>
> This improves the code structure of the ldp-stp policies
> patch introduced in 834fc2bf
>
> Bootstrapped and regtested on aarch64-linux.
>
> gcc/ChangeLog:
> * config/aarch64/aarch64-opts.h (enum aarch64_ldp_policy): Removed.
>
Richard Biener writes:
> On Thu, 28 Sep 2023, Jakub Jelinek wrote:
>
>> Hi!
>>
>> On Tue, Aug 29, 2023 at 05:09:52PM +0200, Jakub Jelinek via Gcc-patches
>> wrote:
>> > On Tue, Aug 29, 2023 at 11:42:48AM +0100, Richard Sandiford wrote:
>> > > > I'll note tree-ssa-loop-niter.cc also uses GMP in
1 - 100 of 142 matches
Mail list logo
