void foo(_Float16 y, int64_t *i64p)
{
vint64m1_t vx =__riscv_vle64_v_i64m1 (i64p, 1);
vx = __riscv_vadd_vv_i64m1 (vx, vx, 1);
vfloat16m1_t vy =__riscv_vfmv_s_f_f16m1 (y, 1);
asm volatile ("# use %0 %1" : : "vr"(vx), "vr" (vy));
}
zve64f:
foo:
vsetivlizero,1,e16,mf4,ta,ma
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111038
--- Comment #1 from Gejoe ---
The document referred was this:
https://gcc.gnu.org/onlinedocs/gcc/Invoking-Gcov.html
Kindly respond to my query.
Eagerly awaited. :)
Thank you very much team for the support !
On Fri, Aug 04, 2023 at 07:44:28PM +, Qing Zhao wrote:
> This is the 2nd version of the patch, per our discussion based on the
> review comments for the 1st version, the major changes in this version
I've been using Coccinelle to find and annotate[1] structures (193 so
far...), and I've
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106769
HaoChen Gui changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110429
HaoChen Gui changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103605
HaoChen Gui changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
on 2023/8/17 11:11, Peter Bergner wrote:
> On 8/16/23 7:19 PM, Carl Love wrote:
>> +(define_insn "dfp_dquan_"
>> + [(set (match_operand:DDTD 0 "gpc_reg_operand" "=d")
>> +(unspec:DDTD [(match_operand:DDTD 1 "gpc_reg_operand" "d")
>> + (match_operand:DDTD 2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110002
--- Comment #3 from Thorsten Otto ---
Created attachment 55745
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55745=edit
Possible workaround
I currently use the attached patch to work around this. However it is a bit
hackish as it uses a
On 8/16/23 19:17, Patrick O'Neill wrote:
This adds new regression tests to ensure half-register rotations are
correctly optimized into rori instructions.
gcc/testsuite/ChangeLog:
* gcc.target/riscv/zbb-rol-ror-08.c: New test.
* gcc.target/riscv/zbb-rol-ror-09.c: New test.
On 8/16/23 02:40, yanzhang.wang--- via Gcc-patches wrote:
From: Yanzhang Wang
The pattern is enabled for scalar but not for vector. The patch try to
make it consistent and will convert below code,
shortcut_for_riscv_vrsub_case_1_32:
vl1re32.v v1,0(a1)
vsetvli
On Tue, 2023-08-15 at 20:03 +, Joseph Myers wrote:
> On Tue, 15 Aug 2023, chenxiaolong wrote:
>
> > In the implementation process, the "q" suffix function is
> > Re-register and associate the "__float128" type with the
> > "long double" type so that the compiler can
Lgtm
Pan Li via Gcc-patches 於 2023年8月17日 週四，11:09寫道：
> From: Pan Li
>
> This patch would like to support the rounding mode API for the
> VFREDUSUM.VS as the below samples.
>
> * __riscv_vfredusum_vs_f32m1_f32m1_rm
> * __riscv_vfredusum_vs_f32m1_f32m1_rm_m
>
> Signed-off-by: Pan Li
>
>
Lgtm
Pan Li via Gcc-patches 於 2023年8月17日 週四，10:19寫道：
> From: Pan Li
>
> This patch would like to support the rounding mode API for the
> VFNCVT.F.{X|XU|F}.W as the below samples.
>
> * __riscv_vfncvt_f_x_w_f32m1_rm
> * __riscv_vfncvt_f_x_w_f32m1_rm_m
> * __riscv_vfncvt_f_xu_w_f32m1_rm
> *
On 8/16/23 13:10, Alexander Monakov wrote:
On Tue, 15 Aug 2023, Jeff Law wrote:
Because if the compiler can optimize it automatically, then the projects have
to do literally nothing to take advantage of it. They just compile normally
and their bitwise CRC gets optimized down to either a
On 8/16/23 7:19 PM, Carl Love wrote:
> +(define_insn "dfp_dquan_"
> + [(set (match_operand:DDTD 0 "gpc_reg_operand" "=d")
> +(unspec:DDTD [(match_operand:DDTD 1 "gpc_reg_operand" "d")
> + (match_operand:DDTD 2 "gpc_reg_operand" "d")
> +
From: Pan Li
This patch would like to support the rounding mode API for the
VFREDUSUM.VS as the below samples.
* __riscv_vfredusum_vs_f32m1_f32m1_rm
* __riscv_vfredusum_vs_f32m1_f32m1_rm_m
Signed-off-by: Pan Li
gcc/ChangeLog:
* config/riscv/riscv-vector-builtins-bases.cc
From: Pan Li
This patch would like to support the rounding mode API for the
VFNCVT.F.{X|XU|F}.W as the below samples.
* __riscv_vfncvt_f_x_w_f32m1_rm
* __riscv_vfncvt_f_x_w_f32m1_rm_m
* __riscv_vfncvt_f_xu_w_f32m1_rm
* __riscv_vfncvt_f_xu_w_f32m1_rm_m
* __riscv_vfncvt_f_f_w_f32m1_rm
*
Thanks Kito, will commit it after the VFNCVT.X.F.W one, aka the signed integer
cvt.
Pan
-Original Message-
From: Kito Cheng
Sent: Thursday, August 17, 2023 9:30 AM
To: Li, Pan2
Cc: gcc-patches@gcc.gnu.org; juzhe.zh...@rivai.ai; Wang, Yanzhang
Subject: Re: [PATCH v1] RISC-V: Support
Hi Dave,
Thanks for the feedback!
On Wed, Aug 16, 2023 at 5:29 PM David Malcolm wrote:
>
> On Wed, 2023-08-16 at 15:17 -0400, Eric Feng via Gcc wrote:
> > Hi everyone,
>
> [fixing typo in my email address]
>
> Hi Eric, thanks for the update, and the WIP patch.
>
> >
> > After pushing the code
Convert be sinked into a vec_cond if both sides
fold. Unlike other unary operations, we need to check that we still can handle
this vec_cond's first operand is the same as the new truth type.
I tried a few different versions of this patch:
view_convert to the new truth_type but that does not work
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110986
--- Comment #18 from CVS Commits ---
The trunk branch has been updated by Andrew Pinski :
https://gcc.gnu.org/g:a32de58c9e6394e4e6aef0ac95b52d1c774ac8bc
commit r14-3257-ga32de58c9e6394e4e6aef0ac95b52d1c774ac8bc
Author: Andrew Pinski
Date:
On Mon, Aug 14, 2023 at 2:54 PM Andrew Pinski wrote:
>
> On Mon, Aug 14, 2023 at 2:37 PM Richard Sandiford via Gcc-patches
> wrote:
> >
> > Andrew Pinski via Gcc-patches writes:
> > > Like the support conditional neg (r12-4470-g20dcda98ed376cb61c74b2c71),
> > > this just adds conditional not
LGTM
On Thu, Aug 17, 2023 at 9:23 AM Pan Li via Gcc-patches
wrote:
>
> From: Pan Li
>
> This patch would like to support the rounding mode API for the
> VFNCVT.XU.F.W as the below samples.
>
> * __riscv_vfncvt_xu_f_w_u16mf2_rm
> * __riscv_vfncvt_xu_f_w_u16mf2_rm_m
>
> Signed-off-by: Pan Li
>
>
From: Pan Li
This patch would like to support the rounding mode API for the
VFNCVT.XU.F.W as the below samples.
* __riscv_vfncvt_xu_f_w_u16mf2_rm
* __riscv_vfncvt_xu_f_w_u16mf2_rm_m
Signed-off-by: Pan Li
gcc/ChangeLog:
* config/riscv/riscv-vector-builtins-bases.cc
This adds new regression tests to ensure half-register rotations are
correctly optimized into rori instructions.
gcc/testsuite/ChangeLog:
* gcc.target/riscv/zbb-rol-ror-08.c: New test.
* gcc.target/riscv/zbb-rol-ror-09.c: New test.
Co-authored-by: Charlie Jenkins
Signed-off-by:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111036
Andrew Pinski changed:
What|Removed |Added
Status|RESOLVED|UNCONFIRMED
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
effective target for the test. Retested the patch on Power 10LE and
Power 8
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111036
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99309
Andrew Pinski changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111027
--- Comment #2 from Andrew Pinski ---
This might fix the issue:
diff --git a/gcc/Makefile.in b/gcc/Makefile.in
index a00dad965c5..267f6258ee3 100644
--- a/gcc/Makefile.in
+++ b/gcc/Makefile.in
@@ -3686,6 +3686,7 @@ install: install-common
On Wed, 16 Aug 2023 15:59:13 PDT (-0700), jeffreya...@gmail.com wrote:
On 8/16/23 07:50, Robin Dapp wrote:
But if it's a float16 precision issue then I would have expected both
the computations for the lhs and rhs values to have suffered
similarly.
Yeah, right. I didn't look closely
On Wed, Aug 16, 2023 at 4:15 PM Patrick O'Neill wrote:
>
> This adds new regression tests to ensure half-register rotations are
> correctly optimized into rori instructions.
>
> gcc/testsuite/ChangeLog:
>
> * gcc.target/riscv/zbb-rol-ror-04.c: Add half-register rotation
> cases.
>
This adds new regression tests to ensure half-register rotations are
correctly optimized into rori instructions.
gcc/testsuite/ChangeLog:
* gcc.target/riscv/zbb-rol-ror-04.c: Add half-register rotation
cases.
* gcc.target/riscv/zbb-rol-ror-05.c: Add half-register rotation
On Wed, 2023-08-16 at 22:06 +0200, Guillaume Gomez via Jit wrote:
> My apologies, forgot to run the commit checkers. Here's the commit
> with the errors fixed.
>
> Le mer. 16 août 2023 à 18:32, Guillaume Gomez
> a écrit :
> >
> > Hi,
Hi Guillaume, thanks for the patch.
> >
> > This patch
On 8/16/23 07:50, Robin Dapp wrote:
But if it's a float16 precision issue then I would have expected both
the computations for the lhs and rhs values to have suffered
similarly.
Yeah, right. I didn't look closely enough. The problem is not the
reduction but the additional return-value
On 8/16/23 14:23, Sergei Trofimovich via Gcc-patches wrote:
From: Sergei Trofimovich
Follow removal of EVRP and clean up unused defines.
gcc/
* flag-types.h (vrp_mode): Remove unused.
OK
jeff
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111037
--- Comment #1 from JuzheZhong ---
confirm
On 09/08/23 01:34 +0300, Vladimir Palevich wrote:
Because of the recent change in _M_realloc_insert and _M_default_append, call
to deallocate was ordered after assignment to class members of std::vector
(in the guard destructor), which is causing said members to be call-clobbered.
This is
On Wed, Aug 16, 2023 at 3:36 PM David Edelsohn via Gcc-patches
wrote:
>
> Was the dependency added to the dependencies in contrib/gcc_update?
> Otherwise the timestamp can get out of sync in a Git checkout.
I checked in https://gcc.gnu.org/pipermail/gcc-patches/2023-August/627667.html
which just
Was the dependency added to the dependencies in contrib/gcc_update?
Otherwise the timestamp can get out of sync in a Git checkout.
Thanks, David
On Wed, Aug 16, 2023 at 6:20 PM Jonathan Wakely wrote:
> On Wed, 16 Aug 2023 at 22:56, Jonathan Wakely wrote:
> >
> > On Wed, 16 Aug 2023 at 22:39,
This adds libstdc++-v3/include/bits/version.h so it has the correct timestamp.
Committed as obvious after running contrib/gcc_update --touch
contrib/ChangeLog:
* gcc_update: Add libstdc++-v3/include/bits/version.h.
---
contrib/gcc_update | 1 +
1 file changed, 1 insertion(+)
diff
On Wed, 2023-08-16 at 14:19 +0200, priour...@gmail.com wrote:
> From: benjamin priour
>
> Hi,
> (s/we/the analyzer/)
Hi Benjamin, thanks for the updated patch.
>
> I've been continuing my patch of supporting operator new variants
> in the analyzer, and have added a few more test cases.
>
>
On Wed, 16 Aug 2023 at 22:56, Jonathan Wakely wrote:
>
> On Wed, 16 Aug 2023 at 22:39, David Edelsohn wrote:
> >
> > Hi, Arsen
> >
> > This patch broke bootstrap because it has introduced a new GCC build
> > requirement for autogen that is not a previous requirement to build GCC.
> >
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102609
--- Comment #6 from waffl3x ---
I've noticed the standard does call `this` a specifier, I will perhaps rework
the code to just do parsing in cp_decl_specifier_seq.
(In reply to Gašper Ažman from comment #5)
> And of course by "this" I meant
On Wed, 16 Aug 2023 at 22:39, David Edelsohn wrote:
>
> Hi, Arsen
>
> This patch broke bootstrap because it has introduced a new GCC build
> requirement for autogen that is not a previous requirement to build GCC.
> Previously the repository has included post-processed files.
The repo does
Hi,
After some more studying and consideration, the following is my thoughts:
For a structure with FMA annotated with counted_by attribute: (the following
small example)
struct annotated {
size_t foo;
char b;
char array[] __attribute__((counted_by (foo)));
};
Hi, Arsen
This patch broke bootstrap because it has introduced a new GCC build
requirement for autogen that is not a previous requirement to build GCC.
Previously the repository has included post-processed files.
+# AutoGen .
+.PHONY: update-version
+update-version:
+ cd ${bits_srcdir} &&
PING
On Tue, Aug 8, 2023 at 8:17 PM Eric Gallager wrote:
>
> On Tue, May 30, 2023 at 5:42 PM Eric Gallager wrote:
> >
> > PR109836 is a request to have -Wpointer-sign enabled by default. There
> > were points of disagreement raised in the bug report, so I figured
> > that maybe as a compromise,
On Wed, 2023-08-16 at 15:17 -0400, Eric Feng via Gcc wrote:
> Hi everyone,
[fixing typo in my email address]
Hi Eric, thanks for the update, and the WIP patch.
>
> After pushing the code that supports various known function classes last week,
> I've turned my attention back to the core
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111009
--- Comment #9 from Sergei Trofimovich ---
Created attachment 55744
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55744=edit
bug.S
At the hazard of stating the obvious: it's a wrong-code when you execute it
(not a gcc ICE).
Should fail
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111009
--- Comment #8 from Andrew Macleod ---
Do I need some special target or something? on trunk just
"-fno-strict-overflow -O3" doesnt fail for me on x86_64-pc-linux-gnu...
./cc1 -fno-strict-overflow -O3 009.c -quiet
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111043
Andrew Pinski changed:
What|Removed |Added
Summary|ICE in |[14 regression] ICE in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111009
--- Comment #7 from Sergei Trofimovich ---
commit bd400db6d3ec167142ace352db00f84d382e33a8 (HEAD)
Date: Fri Oct 15 12:06:27 2021 -0400
Add --param=vrp1-mode and --param=vrp2-mode.
(the first commit that adds the option) generates SIGSEGVs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111043
Bug ID: 111043
Summary: ICE in adjust_loop_info_after_peeling, at
tree-ssa-loop-ivcanon.cc:1068
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity:
> On Aug 16, 2023, at 3:42 PM, Philipp Tomsich wrote:
>
> On Wed, 16 Aug 2023 at 21:10, Alexander Monakov wrote:
>>
>>
>> On Tue, 15 Aug 2023, Jeff Law wrote:
>>
>>> Because if the compiler can optimize it automatically, then the projects
>>> have
>>> to do literally nothing to take
From: Sergei Trofimovich
Follow removal of EVRP and clean up unused defines.
gcc/
* flag-types.h (vrp_mode): Remove unused.
---
gcc/flag-types.h | 7 ---
1 file changed, 7 deletions(-)
diff --git a/gcc/flag-types.h b/gcc/flag-types.h
index 36305de589e..7466c1106f2 100644
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111009
--- Comment #6 from Sam James ---
Can you bisect further back with -param=vrp2-mode=ranger, to force ranger
before it was the default?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111042
Bug ID: 111042
Summary: [OpenMP] 'allocate' clause and combined directive -
impove diagnostic, ICE because of missing diagnostic
Product: gcc
Version: 14.0
Status:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110360
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Target
Dear all,
the attached simple patch fixes a memleak in the frontend when a
character literal is passed to a character,value dummy of a bind(c)
procedure, by relying on gfc_replace_expr to do the cleanup.
(This can be tested e.g. with gfortran.dg/bind_c_usage_13.f03
and running f951 under
FYI, I filed a new PR https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111040
to record this issue.
Qing
> On Aug 16, 2023, at 11:59 AM, Qing Zhao via Gcc-patches
> wrote:
>
> Jakub and Sid,
>
> During my study, I found an interesting behavior for the following small
> testing case:
>
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111009
--- Comment #5 from Sergei Trofimovich ---
For what it's worth bisect pointed at r12-4871-g502ffb1f389011
$ git bisect good
502ffb1f389011b28ee51815242c7397790802d5 is the first bad commit
commit 502ffb1f389011b28ee51815242c7397790802d5
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111040
--- Comment #1 from qinzhao at gcc dot gnu.org ---
an initial study inside gdb shows the following:
1. the guilty pass is "ccp1", when folding the call to
__builtin_dynamic_object_size(p->array, 1)
2. In this pass, the IR for p->array is
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111039
--- Comment #3 from Andrew Pinski ---
I suspect the issue is recognize_single_bit_test does not check
SSA_NAME_OCCURS_IN_ABNORMAL_PHI at all ...
My apologies, forgot to run the commit checkers. Here's the commit
with the errors fixed.
Le mer. 16 août 2023 à 18:32, Guillaume Gomez
a écrit :
>
> Hi,
>
> This patch adds the possibility to specify the __restrict__ attribute
> for function parameters. It is used by the Rust GCC backend.
>
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110942
--- Comment #3 from Andrew Macleod ---
The original revision listed, I narrowed down to a single instance where the
new code did something that makes a difference
we determine that in stmt
stmt _8 = (int) i_10;
which originally had a range of
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111039
--- Comment #2 from Andrew Pinski ---
# flags_1(ab) = PHI
_setjmp (flags_1(ab));
_14 = flags_6(D)(ab) & 9437184;
The use of _6 is the issue here.
The problem shows up in ifcombine pass:
optimizing double bit test to flags_6(D)(ab) & T
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110360
--- Comment #43 from CVS Commits ---
The master branch has been updated by Harald Anlauf :
https://gcc.gnu.org/g:9ade70bb86c8744f4416a48bb69cf4705f00905a
commit r14-3254-g9ade70bb86c8744f4416a48bb69cf4705f00905a
Author: Harald Anlauf
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111039
Andrew Pinski changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111041
Andrew Pinski changed:
What|Removed |Added
Severity|normal |enhancement
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111041
Bug ID: 111041
Summary: Malformed requires syntax should produce better
diagnostics
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
On Wed, 16 Aug 2023 at 21:10, Alexander Monakov wrote:
>
>
> On Tue, 15 Aug 2023, Jeff Law wrote:
>
> > Because if the compiler can optimize it automatically, then the projects
> > have
> > to do literally nothing to take advantage of it. They just compile normally
> > and their bitwise CRC
Hi Alex,
> On 3 Aug 2023, at 10:21, Alex Coplan wrote:
>
> This patch implements clang's __has_feature and __has_extension in GCC.
> This is a v3 which addresses feedback for the v2 patch posted here:
>
> https://gcc.gnu.org/pipermail/gcc-patches/2023-August/626058.html
>
> Main changes
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111040
Bug ID: 111040
Summary: __builtin_object_size: inconsistent result for
subobject with member arrays.
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110942
Andrew Pinski changed:
What|Removed |Added
Last reconfirmed||2023-08-16
Ever confirmed|0
Looks reasonable to me!
On 8/16/23 12:20, Rainer Orth wrote:
On macOS 14, a guard in changed:
-- MacOSX13.3.sdk/usr/include/math.h2023-04-19 01:54:44
+++ MacOSX14.0.sdk/usr/include/math.h 2023-08-01 08:42:43
@@ -22,0 +23 @@
+
@@ -43 +44 @@
-#if __FLT_EVAL_METHOD__ == 0
+#if
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111039
Bug ID: 111039
Summary: Unable to coalesce ssa_names
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
Hi Iain,
> OK, thanks
> (I do not yet have an xcode-15 or darwin23 setup)
Xcode 15 beta claims to also support macOS 13/Darwin 22, though I
haven't tried this.
> After some bake time, this will need backporting to open branches, to avoid
> those also failing in the same way,
Agreed: those
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110426
--- Comment #4 from Alex Henrie ---
I tried out your changes and the warnings look great now. Thank you!
Hi Rainer,
> On 16 Aug 2023, at 20:20, Rainer Orth wrote:
>
> On macOS 14, a guard in changed:
>
> -- MacOSX13.3.sdk/usr/include/math.h 2023-04-19 01:54:44
> +++ MacOSX14.0.sdk/usr/include/math.h 2023-08-01 08:42:43
> @@ -22,0 +23 @@
> +
> @@ -43 +44 @@
> -#if __FLT_EVAL_METHOD__ == 0
> +#if
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110942
--- Comment #1 from Andrew Macleod ---
Created attachment 55743
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55743=edit
patch to revert the change
Although the bisection stopped at this change, it does not appear to be the
underlying
Hi Rainer,
> On 16 Aug 2023, at 20:13, Rainer Orth wrote:
>
> Since Xcode 15 beta 6, ld -v output differs from previous versions:
>
> * macOS 13/Xcode 14:
>
> @(#)PROGRAM:ld PROJECT:ld64-857.1
>
> * macOS 14/Xcode 15:
>
> @(#)PROGRAM:ld PROJECT:dyld-1015.1
>
> configure cannot handle
On macOS 14, a guard in changed:
-- MacOSX13.3.sdk/usr/include/math.h2023-04-19 01:54:44
+++ MacOSX14.0.sdk/usr/include/math.h 2023-08-01 08:42:43
@@ -22,0 +23 @@
+
@@ -43 +44 @@
-#if __FLT_EVAL_METHOD__ == 0
+#if __FLT_EVAL_METHOD__ == 0 || __FLT_EVAL_METHOD__ == -1
@@ -49 +50 @@
-#elif
Hi everyone,
After pushing the code that supports various known function classes last week,
I've turned my attention back to the core reference count checking
functionality. This functionality used to reside in region_model, which
wasn't ideal. To address this, I've introduced a hook to
Since Xcode 15 beta 6, ld -v output differs from previous versions:
* macOS 13/Xcode 14:
@(#)PROGRAM:ld PROJECT:ld64-857.1
* macOS 14/Xcode 15:
@(#)PROGRAM:ld PROJECT:dyld-1015.1
configure cannot handle the new form, so LD64_VERSION isn't set.
This patch fixes this. The autoconf
On Tue, 15 Aug 2023, Jeff Law wrote:
> Because if the compiler can optimize it automatically, then the projects have
> to do literally nothing to take advantage of it. They just compile normally
> and their bitwise CRC gets optimized down to either a table lookup or a clmul
> variant. That's
Tested x86_64-linux, pushed to trunk. This should be backported to
gcc-12 and gcc-13 too (without the std::format test changes).
-- >8 --
The callable used for resize_and_overwrite was being passed the string's
expanded capacity, which might be greater than the new size being
requested. This is
Tested x86_64-linux, pushed to trunk.
-- >8 --
libstdc++-v3/ChangeLog:
* include/bits/version.def (stds): Update value for C++23.
* include/bits/version.h: Regenerate.
---
libstdc++-v3/include/bits/version.def | 2 +-
libstdc++-v3/include/bits/version.h | 72
Hi Rainer!
On Tue, 2023-08-15 21:49:37 +0200, Rainer Orth
wrote:
> > config-list.mk Darwin: Use --with-gnu-as for mass-building tests
> >
> > As `config-list.mk` is probably mostly used on Linux system, where
> > Apple's tools aren't around. Let's use --with-gnu-as instead to have
> > an
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102609
--- Comment #5 from Gašper Ažman ---
And of course by "this" I meant support for a default argument on the explicit
object parameter.
We might add it back in the future if we find a usecase.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102609
--- Comment #4 from Gašper Ažman ---
As one of the authors, I can assure you you never need to implement this for
c++23.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102609
--- Comment #3 from waffl3x ---
I have some elements working so far, I opted to implement parsing for `this` in
cp_parser_parameter_declaration instead of in cp_parser_decl_specifier_seq
because I didn't want to add another member to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111038
Bug ID: 111038
Summary: The function summary in gcov
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: gcov-profile
On 09/08/23 01:34 +0300, Vladimir Palevich wrote:
Because of the recent change in _M_realloc_insert and _M_default_append, call
to deallocate was ordered after assignment to class members of std::vector
(in the guard destructor), which is causing said members to be call-clobbered.
This is
On Wed, 16 Aug 2023 at 17:06, Patrick Palka via Libstdc++
wrote:
>
> On Sun, Apr 16, 2023 at 11:24 PM Patrick Palka wrote:
> >
> > On Fri, 14 Apr 2023, Patrick Palka wrote:
> >
> > > Using the CRTP idiom for this base class avoids bloating the size of a
> > > pipeline when adding distinct empty
On Wed, 16 Aug 2023 at 17:07, Patrick Palka via Libstdc++
wrote:
>
> On Mon, Apr 24, 2023 at 12:23 PM Patrick Palka wrote:
> >
> > This patch makes these integer-class type structural types by changing
> > their private data members into public ones, which allows them to be
> > used as NTTP
On Wed, 16 Aug 2023 at 17:05, Patrick Palka via Libstdc++
wrote:
>
> On Mon, Apr 17, 2023 at 9:39 AM Patrick Palka wrote:
> >
> > This C++23 paper fixes a bug in these views when adapting a certain kind
> > of non-forward range, and we treat it as a DR against C++20.
> >
> > Tested on
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110254
--- Comment #3 from CVS Commits ---
The master branch has been updated by Surya Kumari Jangala
:
https://gcc.gnu.org/g:02ecc9a26324d142c5cd19d24526b9c23aabc1c3
commit r14-3251-g02ecc9a26324d142c5cd19d24526b9c23aabc1c3
Author: Surya Kumari
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110927
Patrick Palka changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
Yes, the other files are in another committee proposal, and I'm working my
way through the proposals one by one.
Thank you for the feedback, I'll update and resend
/Paul
Den ons. 16. aug. 2023 kl. 15.51 skrev Arsen Arsenović :
>
> Jonathan Wakely writes:
>
> > On Fri, 21 Jul 2023 at 22:23, Paul
1 - 100 of 188 matches
Mail list logo
