This patch fixes the 2nd parameter name mismatch in
ARRAYOFCHAR.mod.
gcc/m2/ChangeLog:
PR modula2/121164
* gm2-libs/ARRAYOFCHAR.mod (Write): Rename 2nd parameter
name a to str.
(cherry picked from commit 22d8b89689769e5efefd2c4e6dda88d9f0b2a945)
Signed-off-by: Gaius Mu
Dear all,
the attached simple and obvious patch fixes an erroneous runtime check
with -fcheck=pointer when passing a non-associated proc-pointer to an
optional dummy.
Regtested on x86_64-pc-linux-gnu. OK for mainline / backports?
Thanks,
Harald
From 8f9450505f8244d262f8b4ff274f113f99cdc7e2 Mo
This patch fixes the 2nd parameter name mismatch in
ARRAYOFCHAR.mod.
gcc/m2/ChangeLog:
PR modula2/121164
* gm2-libs/ARRAYOFCHAR.mod (Write): Rename 2nd parameter
name a to str.
Signed-off-by: Gaius Mulley
---
gcc/m2/gm2-libs/ARRAYOFCHAR.mod | 6 +++---
1 file changed,
Ping^3
在 2025/5/27 上午8:54, Lulu Cheng 写道:
Ping^2
在 2025/5/13 下午2:06, Lulu Cheng 写道:
Ping?
在 2025/5/9 上午10:14, Lulu Cheng 写道:
From: ChengLulu
PR target/99217
gcc/ChangeLog:
* config/mips/mips.cc (mips_start_function_definition):
Implements the functionality of '-fpatchable-fun
Good evening,
Thanks for the feedback! I'll get a v4 done with the following changes:
- charT, traits capitalization
- remove accidental whitespace changes
- remove unnecessary this->/{}
- redundant parens - I suspect you're correct, I will validate and make the
change accordingly. If it persists
On Fri, 18 Jul 2025, 18:51 Jonathan Wakely, wrote:
> When the C++98 std::distance and std::advance functions (and C++11
> std::next and std::prev) are used with C++20 iterators there can be
> unexpected results, ranging from compilation failure to decreased
> performance to undefined behaviour.
>
On Fri, 18 Jul 2025, 1nfocalypse wrote:
> Implements Philox Engine (P2075R6) and associated tests.
>
> Additionally implements changes based on feedback from Patrick
> Palka and jwakely on v2.
>
> Regarding the question posed by Patrick on why some things are
> defined inline and some out of lin
On Fri, 18 Jul 2025 at 19:18, Tomasz Kaminski wrote:
>
>
>
> On Fri, Jul 18, 2025 at 8:03 PM Jonathan Wakely wrote:
>>
>> This adds a check when incrementing the shared count and weak count and
>> will trap if it overflows. This also double the effective range of the
>> counts for most 64-bit tar
Hi Andre,
Am 18.07.25 um 21:41 schrieb Andre Vehreschild:
Hi Harald,
that looks fine to me. Ok to commit and backport. Thanks for the patch.
pushed as r16-2355-g8f9450505f8244 so far.
Thanks for the review!
Harald
- Andre
Andre Vehreschild * ve...@gmx.de
Am 18. Juli 2025 21:19:00 schrieb
Currently this new concept will get defined for -std=c++17 -fconcepts
but as it uses std::input_iterator, which is new in C++20, that won't
work. Guard it with __cpp_lib_concepts as well as __cpp_concepts.
libstdc++-v3/ChangeLog:
* include/bits/stl_iterator_base_types.h (__any_input_itera
On Fri, Jul 18, 2025, at 9:45 AM, Hans-Peter Nilsson wrote:
> From: Hans-Peter Nilsson
>
> This has an effect only for MMIX and BPF. All other targets are
> either 32-bits-or-less BITS_PER_WORD (and will now get 64 just
> by a more obvious expression), or they don't use the default
> MAX_FIXED_MO
From: Pan Li
The previous test case doesn't leverage the right test helper macro,
it should be DEF_AVG_0_WRAP instead of DEF_AVG_0. We prefer the
test function name is test_avg_floor_int64_t_int32_t_0 instead
of test_avg_floor_WT_NT_0 for DEF_AVG_0(WT, NT).
The below test suites are passed for
On Thu, Jul 17, 2025 at 06:44:08PM -0400, Jason Merrill wrote:
> On 7/17/25 6:25 PM, Jakub Jelinek wrote:
> > On Thu, Jul 17, 2025 at 05:31:27PM -0400, Jason Merrill wrote:
> > > On 7/16/25 10:49 AM, Marek Polacek wrote:
> > > > Bootstrapped/regtested on x86_64-pc-linux-gnu, ok for trunk?
> > > >
On Fri, 18 Jul 2025 at 19:03, Jonathan Wakely wrote:
>
> This adds a check when incrementing the shared count and weak count and
> will trap if it overflows. This also double the effective range of the
> counts for most 64-bit targets.
>
> The counter type, _Atomic_word, is usually a signed 32-bit
On Fri, 18 Jul 2025 at 12:22, Tomasz Kaminski wrote:
>
>
>
> On Fri, Jul 18, 2025 at 12:52 PM Nathan Myers wrote:
>>
>> * I rewrote the implementation to more closely resemble the
>> non-NTTP version, and fix the various noexcept and requires
>> omissions.
>
> I have a task to adjust them late
Hi Harald,
that looks fine to me. Ok to commit and backport. Thanks for the patch.
- Andre
Andre Vehreschild * ve...@gmx.de
Am 18. Juli 2025 21:19:00 schrieb Harald Anlauf :
Dear all,
the attached simple and obvious patch fixes an erroneous runtime check
with -fcheck=pointer when passing a no
On Thu, Jul 17, 2025 at 05:20:31PM -0400, Jason Merrill wrote:
> On 7/16/25 5:59 PM, Marek Polacek wrote:
> > On Mon, Jul 14, 2025 at 12:52:41PM -0400, Jason Merrill wrote:
> > > On 7/11/25 5:49 PM, Marek Polacek wrote:
> > > > On Thu, Jul 10, 2025 at 02:13:06PM -0400, Jason Merrill wrote:
> > > >
On Thu, Jul 17, 2025 at 7:02 PM Jonathan Wakely wrote:
> This implements the missing functions in _Utf_iterator to support
> reverse iteration. All existing tests pass when the view is reversed, so
> that the same code units are seen when iterating forwards or backwards.
>
> libstdc++-v3/ChangeLo
On Thu, 17 Jul 2025, Martin Jambor wrote:
> Hi,
>
> testcase of PR 117423 shows a flaw in the fancy way we do "total
> scalarization" in SRA now. We use the types encountered in the
> function body and not in type declaration (allowing us to totally
> scalarize when only one union field is ever
On Thu, 17 Jul 2025, Jakub Jelinek wrote:
> Hi!
>
> The following testcase ICEs because SCALAR_INT_TYPE_MODE of course
> doesn't work for large BITINT_TYPE types which have BLKmode.
> native_encode* as well as e.g. r14-8276 use in cases like these
> GET_MODE_SIZE (SCALAR_INT_TYPE_MODE ()) and TRE
This patch reformats three comments in the GNU GCC style.
gcc/m2/ChangeLog:
* gm2-compiler/M2GCCDeclare.mod (StartDeclareModuleScopeSeparate):
Reformat statement comments.
(StartDeclareModuleScopeWholeProgram): Ditto.
(cherry picked from commit 7a7cc65b8987b9b05fb8fb758
The PR shows that the uninit analysis limits are set too low in
cases we lower switches to ifs as happens on s390x for a linux
kernel TU. This causes false positive uninit diagnostics as we
abort the attempt to prove that a value is initialized on all
paths. The new testcase only would require up
On Fri, Jul 18, 2025 at 09:07:35AM +0200, Richard Biener wrote:
> The PR shows that the uninit analysis limits are set too low in
> cases we lower switches to ifs as happens on s390x for a linux
> kernel TU. This causes false positive uninit diagnostics as we
> abort the attempt to prove that a va
From: Javier Miranda
gcc/ada/ChangeLog:
* exp_aggr.adb (Gen_Assign): Code cleanup.
(Initialize_Component): Do not adjust the tag when the type of
the aggregate components is a mutably tagged type.
Tested on x86_64-pc-linux-gnu, committed on master.
---
gcc/ada/exp_aggr
Hi Thomas,
> In PR119692 "C++ 'typeinfo', 'vtable' vs. OpenACC, OpenMP 'target'
> offloading":
>
>> --- Comment #8 from Rainer Orth ---
>> The last commit made things worse on sparc-sun-solaris2.11: since that one
>> (dg-timeout 10) I regularly get
>>
>> WARNING: libgomp.c++/target-exceptions-ba
On 18/07/25 13:22, Filip Kastl wrote:
External email: Use caution opening links or attachments
Hi,
I've tried running it and quickly looked through the code. Looks good to me!
I'm not a mantainer, though.
Just two nitpicks from me inline...
On Wed 2025-07-16 21:47:00, dhr...@nvidia.com wrot
From: Gary Dismukes
The compiler incorrectly treats an overriding private subprogram that
should not be visible outside a package (because it only overrides in
the private part) as a possible interpretation for a call using prefixed
notation outside of the package. This can result in an ambiguity
* Andrew
On Mon, Jul 14, 2025 at 08:51:01AM -0700, Andrew Pinski wrote:
> On Mon, Jul 14, 2025 at 5:32 AM Yury Khrustalev
> wrote:
> >
> > ...
> >
> > Regression has been checked on AArch64 and no regression has been
> > found. OK for trunk?
>
> I think this is ok. I assume you tested it with b
Hi Segher,
On 7/17/2025 10:20 PM, Segher Boessenkool wrote:
CAUTION: This email comes from a non Wind River email account!
Do not click links or open attachments unless you recognize the sender and know
the content is safe.
Hi!
On Thu, Jul 17, 2025 at 05:58:47AM -0700, harish.sadin...@windriv
On Fri, 18 Jul 2025 at 07:59, Tomasz Kaminski wrote:
>
>
>
> On Thu, Jul 17, 2025 at 7:02 PM Jonathan Wakely wrote:
>>
>> This implements the missing functions in _Utf_iterator to support
>> reverse iteration. All existing tests pass when the view is reversed, so
>> that the same code units are s
This implements the missing functions in _Utf_iterator to support
reverse iteration. All existing tests pass when the view is reversed, so
that the same code units are seen when iterating forwards or backwards.
libstdc++-v3/ChangeLog:
* include/bits/unicode.h (_Utf_iterator::operator--):
I incorrectly assumed that all targets that support __int128 use the
LP64 ABI, so size_t is a 64-bit type. But x32 uses ILP32 and still
supports __int128 (because it's an ILP32 target on 64-bit hardware).
Add casts to the tests so that we get the correct expected values using
size_t type.
libstdc
Hi all,
For inserting zero into a vector lane we usually use an instruction like:
ins v0.h[2], wzr
This, however, has not-so-great performance on some CPUs.
On Grace, for example it has a latency of 5 and throughput 1.
The alternative sequence:
moviv31.8b, #0
ins
Hi all,
The rtx costs logic for CONST_VECTOR, VEC_DUPLICATE and VEC_SELECT sets
the cost unconditionally to the movi, dup or extract fields of extra_cost,
when the normal practice in that function is to use extra_cost only when speed
is set. When speed is false the function should estimate the si
From: Harish Sadineni
Avoid encoding full build paths into file headers, use only the
basename of the source file. This improves build reproducibility,
particularly in environments where build paths vary and source
files are saved for debugging.
For example, in addkf3-sw.c the file header previo
Added changelog entries.
-- >8 --
If a check-function-bodies test is compiled using -fstack-protector*,
-fhardened, -fstack-check*, or -fstack-clash-protection, but the test is
not asking explicitly for those via dg-options or
dg-additional-options, then mark the test as unsupported. Since these
> Hi,
>
> Thanks for the review! No, there is no reason for it being CamelCase. I had
> written
> the code in CamelCase originally then 'sed s/CamelCase/snake_case/g'd the
> functions.
> I forgot to update this one :)
>
> Looks like I also forgot to update the Colors class as well.
I'd actuall
Hi Segher,
On 7/18/2025 1:36 PM, Segher Boessenkool wrote:
CAUTION: This email comes from a non Wind River email account!
Do not click links or open attachments unless you recognize the sender and know
the content is safe.
Hi!
On Fri, Jul 18, 2025 at 01:29:07PM +0530, Harish Sadineni wrote:
Implements Philox Engine (P2075R6) and associated tests.
Additionally implements changes based on feedback from Patrick
Palka and jwakely on v2.
Regarding the question posed by Patrick on why some things are
defined inline and some out of line, things were either defined inline
either due to bein
This patch introduces the procedure GetFile into the supplementary
ISO style library IOChanUtils.
gcc/m2/ChangeLog:
PR modula2/120912
* gm2-libs-iso/IOChanUtils.def (GetFile): New procedure function.
* gm2-libs-iso/IOChanUtils.mod (GetFile): New procedure function.
(che
Hi,
I've tried running it and quickly looked through the code. Looks good to me!
I'm not a mantainer, though.
Just two nitpicks from me inline...
On Wed 2025-07-16 21:47:00, dhr...@nvidia.com wrote:
> From: Dhruv Chawla
>
> This is a script that makes it easier to visualize the output from ma
Hi!
On Fri, Jul 18, 2025 at 01:29:07PM +0530, Harish Sadineni wrote:
> > Okay for trunk (with the commit message improved). Thank you!
> Thank you for the review.
> I have updated the commit message as you suggested and sent a v3.
Which I pre-approved, eh :-) And it does look good, please commi
From: Bob Duff
...because it breaks one test that uses --RTS=light.
"Is_Composite_Type" is needed; "not Is_Scalar_Type"
was wrong.
gcc/ada/ChangeLog:
* tbuild.adb (Unchecked_Convert_To): Back out
change.
Tested on x86_64-pc-linux-gnu, committed on master.
---
gcc/ada/tbuild.a
From: Steve Baird
In some cases involving a generic with two formal parameters, a formal package
and a formal derived type that is derived from an interface type declared in
the formal package, a legal instantiation of that generic is rejected with a
message incorrectly stating that the second ac
From: Piotr Trojanek
For non-instance units GNAT builds elaboration entities before the ghost mode
is inherited from those units. However, for generic instances GNAT was building
elaboration entities with ghost mode inherited from those instances, which
effectively caused elaboration entities to
When inlining function calls that return on the secondary stack used as
function actual or in a return statement, the compiler creates an
invalid GNAT Tree with a variable of an unconstrained type without an
initializer.
Also add an extra assertion to catch problematic cases directly in
Expand_Inl
This removes paths gated by !slp_node and propagates out ncopies == 1,
thereby reducing the vectorizable_live_operation_1 API.
Bootstrapped and tested on x86_64-unknown-linux-gnu, pushed.
* tree-vect-loop.cc (vectorizable_live_operation_1):
Remove stmt_info and ncopies parameters.
Previously for localized output, if _M_debug option was send, the _M_check_ok
completed succesfully and _M_locale_fmt was called for months/weekdays that
are !ok().
This patch lifts debug checks from each conversion function into _M_check_ok,
that in case of !ok() values return a string_view conta
On Fri, 18 Jul 2025 at 11:04, Tomasz Kamiński wrote:
>
> Previously for localized output, if _M_debug option was send, the _M_check_ok
> completed succesfully and _M_locale_fmt was called for months/weekdays that
> are !ok().
>
> This patch lifts debug checks from each conversion function into _M_
I am at a point where I want to store additional information from
analysis (from loads and stores) to re-use them at transform stage
without repeating the analysis. I do not want to add to
stmt_vec_info at this point, so this starts adding kind specific
sub-structures by moving the STMT_VINFO_TYPE
Hi!
On 2025-04-26T00:09:21+, ci_notify--- via Gcc-regression
wrote:
> Our automatic CI has detected problems related to your patch(es). Please find
> some details below.
>
> In gcc_check master-arm, after:
> | commit gcc-16-130-gaafe942227b
> | Author: Thomas Schwinge
> | Date: Wed
Previously for localized output, if _M_debug option was send, the _M_check_ok
completed succesfully and _M_locale_fmt was called for months/weekdays that
are !ok().
This patch lifts debug checks from each conversion function into _M_check_ok,
that in case of !ok() values return a string_view conta
Thanks Ciyan, a nit for asm check.
+/* { dg-do compile } */
+/* { dg-options "-march=rv64gc -mabi=lp64d -fdump-tree-optimized" } */
+
+#include "sat_arith.h"
+
+DEF_SAT_U_ADD_FMT_8(uint16_t)
+
+/* { dg-final { scan-tree-dump-times ".SAT_ADD " 1 "optimized" } } */
Can we add /* { dg-final { scan-a
On 7/18/25 05:39, Kyrylo Tkachov wrote:
> External email: Use caution opening links or attachments
>
>
> Hi all,
>
> For inserting zero into a vector lane we usually use an instruction like:
> ins v0.h[2], wzr
>
> This, however, has not-so-great performance on some CPUs.
> On Grace, f
On Fri, Jul 18, 2025 at 3:04 PM Jonathan Wakely wrote:
> On 18/07/25 14:01 +0200, Tomasz Kamiński wrote:
> >Previously for localized output, if _M_debug option was send, the
> _M_check_ok
> >completed succesfully and _M_locale_fmt was called for months/weekdays
> that
> >are !ok().
> >
> >This pa
For master, let's change the default; see other recent patch.
Committed to gcc-15 branch.
Pietro, thanks again for the patch that led up to this. This is
in a different place and with different contents, but you made
the first move in this direction so IMHO attribution is in order.
-- >8 --
Be
Ok to apply removal of backends no more present in v13?
Johann
--
backends.html (cr16, tilegx, tilepro): Remove entries.
The cr16, tilegx and tilepro backends have been removed in v13,
which is the oldest supported GCC release.
diff --git a/htdocs/backends.html b/htdocs/backends.html
index 52
Hi,
Sorry for the very long delay (more than one year O.o).
I finally took time to apply suggestions and to update the patch to be
up-to-date.
Joined to this email.
Cordially.
Le mer. 26 juin 2024 à 17:10, David Malcolm a écrit :
>
> On Mon, 2024-04-22 at 19:56 +0200, Guillaume Gomez wrote:
On 7/18/25 8:37 AM, Georg-Johann Lay wrote:
Ok to apply removal of backends no more present in v13?
Yes.
jeff
Hello, gentle maintainer.
This is a message from the Translation Project robot.
A revised PO file for textual domain 'cpplib' has been submitted
by the Serbian team of translators. The file is available at:
https://translationproject.org/latest/cpplib/sr.po
(This file, 'cpplib-15.1-b202503
cpplib-15.1-b20250316.sr.po.gz
Description: Binary data
The Translation Project robot, in the
name of your translation coordinator.
Hi Andre,
After a false start, the patch was applied to mainline, did what it was
supposed to do and regtests fine.
Ok for mainline.
Thanks
Paul
On Fri, 18 Jul 2025 at 13:42, Andre Vehreschild wrote:
> Hi all, hi Harald,
>
> attached patch fixes a runtime out-of-bounds error when an iterato
Hi Kyrill,
> -Original Message-
> From: Kyrylo Tkachov
> Sent: Friday, July 18, 2025 10:40 AM
> To: GCC Patches
> Cc: Tamar Christina ; Richard Sandiford
> ; Alex Coplan ; Andrew
> Pinski
> Subject: [PATCH 1/2] aarch64: NFC - Make vec_* rtx costing logic consistent
>
> Hi all,
>
> The
I missed this when I added the two testcase vect-reduc-cond-[12].c. These
testcases
require support of vectorization of `a ? b : c` which some targets (e.g. sparc)
does
not support.
Pushed as obvious after a quick test.
PR testsuite/121153
gcc/testsuite/ChangeLog:
* gcc.dg/vect
libstdc++-v3/ChangeLog:
* doc/xml/manual/build_hacking.xml: Document that
windows_zones-map.h is a generated file.
* doc/html/manual/appendix_porting.html: Regenerate.
---
Pushed to trunk.
libstdc++-v3/doc/html/manual/appendix_porting.html | 7 +++
libstdc++-v3/doc/
Paolo has not been active for some time.
libstdc++-v3/ChangeLog:
* doc/xml/manual/appendix_contributing.xml: Remove Paolo from
list of maintainers to contact about contributing.
* doc/html/manual/appendix_contributing.html: Regenerate.
---
Pushed to trunk.
libstdc++-v3/
Hi Tamar,
> On 18 Jul 2025, at 18:25, Tamar Christina wrote:
>
> Hi Kyrill,
>
>> -Original Message-
>> From: Kyrylo Tkachov
>> Sent: Friday, July 18, 2025 10:40 AM
>> To: GCC Patches
>> Cc: Tamar Christina ; Richard Sandiford
>> ; Alex Coplan ; Andrew
>> Pinski
>> Subject: [PATCH 1/2]
On Wed, Jul 02, 2025 at 08:15:40PM -0600, Jeff Law wrote:
> A number of folks have had their fingers in this code and it's going to take
> a few submissions to do everything we want to do.
>
> This patch is primarily concerned with avoiding signaling that fusion can
> occur in cases where it obvio
On Fri, 18 Jul 2025, Jeff Law wrote:
> On 7/18/25 8:37 AM, Georg-Johann Lay wrote:
>> Ok to apply removal of backends no more present in v13?
> Yes.
And feel free to simply push such changes (under the obvious rule).
Gerald
Hi Jennifer,
> On 18 Jul 2025, at 17:08, Jennifer Schmitz wrote:
>
>
>
>> On 18 Jul 2025, at 11:39, Kyrylo Tkachov wrote:
>>
>> External email: Use caution opening links or attachments
>>
>>
>> Hi all,
>>
>> For inserting zero into a vector lane we usually use an instruction like:
>>
On 7/18/25 11:03 AM, Artemiy Volkov wrote:
On Wed, Jul 02, 2025 at 08:15:40PM -0600, Jeff Law wrote:
A number of folks have had their fingers in this code and it's going to take
a few submissions to do everything we want to do.
This patch is primarily concerned with avoiding signaling that f
When the C++98 std::distance and std::advance functions (and C++11
std::next and std::prev) are used with C++20 iterators there can be
unexpected results, ranging from compilation failure to decreased
performance to undefined behaviour.
An iterator which satisfies std::input_iterator but does not
On Fri, Jul 18, 2025 at 12:52 PM Nathan Myers wrote:
> * I rewrote the implementation to more closely resemble the
> non-NTTP version, and fix the various noexcept and requires
> omissions.
>
I have a task to adjust them later, so the alignment may not be desired.
>
> * I don't understand wh
There's a new compiler warning breaking the build. This fixes it. The
variable appears to be genuinely vestigial.
libgomp/ChangeLog:
PR target/121156
* config/gcn/bar.c (gomp_team_barrier_wait_end): Remove unused
"generation" variable.
(gomp_team_barrier_wait_can
Previously for localized output, if _M_debug option was send, the _M_check_ok
completed succesfully and _M_locale_fmt was called for months/weekdays that
are !ok().
This patch lifts debug checks from each conversion function into _M_check_ok,
that in case of !ok() values return a string_view conta
On 18/07/25 14:01 +0200, Tomasz Kamiński wrote:
Previously for localized output, if _M_debug option was send, the _M_check_ok
completed succesfully and _M_locale_fmt was called for months/weekdays that
are !ok().
This patch lifts debug checks from each conversion function into _M_check_ok,
that
> OK. Curious if you've seen this show up in practice and is using the
> vaaddu and similar instructions actually profitable?
I remember avg will be presented in somewhere else but not for DImode.
I tried to add vaadd related vx combine and notice we don't have DImode for
rvv, so make it availa
* I rewrote the implementation to more closely resemble the
non-NTTP version, and fix the various noexcept and requires
omissions.
* I don't understand what "a separate type for single argument
case, that correspond to function_ref nontype, ptr/ref constructor"
means, but I did make no-boun
The following is a start to how we handle gather/scatter, in
particular at this point we are re-doing stmt-based analysis
at many points but with SLP we're doing that only on the
representative for later analyses. The following does a first
step in trying to remember the dataref analysis result
(a
Hi all, hi Harald,
attached patch fixes a runtime out-of-bounds error when an iterator of an
implied do-loop was not substituted as expected. The resulting code would still
use the uninitialized iterator variable which then lead to out-of-bounds
accesses.
Harald, I did not look at the patch you p
Previously for localized output, if _M_debug option was set, the _M_check_ok
completed succesfully and _M_locale_fmt was called for months/weekdays that
are !ok().
This patch lifts debug checks from each conversion function into _M_check_ok,
that in case of !ok() values return a string_view contai
PR libstdc++/119137
libstdc++-v3/ChangeLog:
* include/std/inplace_vector (inplace_vector::operator=):
Qualify call to std::addressof.
---
Thank's Patrick for pointing this out. Pushed to trunk.
libstdc++-v3/include/std/inplace_vector | 4 ++--
1 file changed, 2 insertion
From: Hans-Peter Nilsson
This has an effect only for MMIX and BPF. All other targets are
either 32-bits-or-less BITS_PER_WORD (and will now get 64 just
by a more obvious expression), or they don't use the default
MAX_FIXED_MODE_SIZE.
I can't build a complete toolchain for BPF (fails building
li
Can the risc-v people try to sort out this up to a point
where I can just s/STMT_VINFO_TYPE/SLP_TREE_TYPE there?
I think for us this mainly (only?) concerns the dynamic LMUL heuristic.
Currently we go through all vectorized instructions of the loop's blocks,
lookup the stmt_vec_info and then get
On Fri, Jul 18, 2025 at 8:03 PM Jonathan Wakely wrote:
> This adds a check when incrementing the shared count and weak count and
> will trap if it overflows. This also double the effective range of the
> counts for most 64-bit targets.
>
> The counter type, _Atomic_word, is usually a signed 32-bi
The standard requires that std::atomic::fetch_add does
not have undefined behaviour for signed overflow, instead it wraps like
unsigned integers. The compiler ensures this is true for the atomic
built-ins that std::atomic uses, but it's not currently true for the
__gnu_cxx::__exchange_and_add and _
This adds a check when incrementing the shared count and weak count and
will trap if it overflows. This also double the effective range of the
counts for most 64-bit targets.
The counter type, _Atomic_word, is usually a signed 32-bit int (except
on Solaris v9 where it is a signed 64-bit long). The
On Fri, Jul 18, 2025 at 11:42:59AM -0600, Jeff Law wrote:
>
>
> On 7/18/25 11:03 AM, Artemiy Volkov wrote:
> > On Wed, Jul 02, 2025 at 08:15:40PM -0600, Jeff Law wrote:
> > > A number of folks have had their fingers in this code and it's going to
> > > take
> > > a few submissions to do everythi
Hello,
On 7/11/25 6:47 PM, Martin Jambor wrote:
Hello,
and sorry for a rather late reaction. First and foremost, thanks for
the patch, I think it is great to have this finally implemented and
although I would like to see a couple things changed, I think the patch
is quite close to what could b
89 matches
Mail list logo
