On Tue, 22 Apr 2025, Richard Sandiford wrote:
> Ping, since it sounds from irc like the release is coming soon :)
Fine with me.
> Richard Sandiford writes:
> > gcc.dg/tree-ssa/predcom-8.c fails on aarch64 for the reasons discussed
> > in the PR trail. The fix didn't
Ping, since it sounds from irc like the release is coming soon :)
Richard Sandiford writes:
> gcc.dg/tree-ssa/predcom-8.c fails on aarch64 for the reasons discussed
> in the PR trail. The fix didn't make it into GCC 15, so this patch
> XFAILs the test instead.
>
> Other t
On Mon, Apr 21, 2025 at 4:30 PM H.J. Lu wrote:
>
> On Mon, Apr 21, 2025 at 11:29 AM Hongtao Liu wrote:
> >
> > On Sat, Apr 19, 2025 at 1:25 PM H.J. Lu wrote:
> > >
> > > On Sun, Dec 1, 2024 at 7:50 AM H.J. Lu wrote:
> > > >
> > > > For all different modes of all 0s/1s vectors, we can use the si
On Mon, Apr 21, 2025 at 11:29 AM Hongtao Liu wrote:
>
> On Sat, Apr 19, 2025 at 1:25 PM H.J. Lu wrote:
> >
> > On Sun, Dec 1, 2024 at 7:50 AM H.J. Lu wrote:
> > >
> > > For all different modes of all 0s/1s vectors, we can use the single widest
> > > all 0s/1s vector register for all 0s/1s vector
On Sat, Apr 19, 2025 at 1:25 PM H.J. Lu wrote:
>
> On Sun, Dec 1, 2024 at 7:50 AM H.J. Lu wrote:
> >
> > For all different modes of all 0s/1s vectors, we can use the single widest
> > all 0s/1s vector register for all 0s/1s vector uses in the whole function.
> > Add a pass to generate a single wi
Hi all,
I’d like to ping the patch from April 2024 at
https://gcc.gnu.org/pipermail/gcc-patches/2024-May/651100.html
As far as I understand, the status of this is:
- Iain posted the patch for review
- Richard said "your target hook is reasonable though I'd name it
expand_unreachab
On Sat, Apr 19, 2025 at 4:16 PM Uros Bizjak wrote:
>
> On Sat, Apr 19, 2025 at 7:22 AM H.J. Lu wrote:
> >
> > On Mon, Dec 2, 2024 at 6:27 AM H.J. Lu wrote:
> > >
> > > Add pcmpeq splitters to split
> > >
> > > (insn 5 3 7 2 (set (reg:V4SI 100)
> > > (eq:V4SI (reg:V4SI 98)
> > >
"Alpha:
> > > Also use tree information to get base block alignment") regression.
> >
> > Ping for:
> > <https://inbox.sourceware.org/gcc-patches/alpine.deb.2.21.2502251934260.65...@angie.orcam.me.uk/>.
> OK. Clearly this one slipped through the cracks.
e0dae4da4c45 ("Alpha:
Also use tree information to get base block alignment") regression.
Ping for:
<https://inbox.sourceware.org/gcc-patches/alpine.deb.2.21.2502251934260.65...@angie.orcam.me.uk/>.
OK. Clearly this one slipped through the cracks.
jeff
On Sat, Apr 19, 2025 at 7:22 AM H.J. Lu wrote:
>
> On Mon, Dec 2, 2024 at 6:27 AM H.J. Lu wrote:
> >
> > Add pcmpeq splitters to split
> >
> > (insn 5 3 7 2 (set (reg:V4SI 100)
> > (eq:V4SI (reg:V4SI 98)
> > (reg:V4SI 98))) 7910 {*sse2_eqv4si3}
> > (expr_list:REG_DEAD (re
On Sun, Dec 1, 2024 at 7:50 AM H.J. Lu wrote:
>
> For all different modes of all 0s/1s vectors, we can use the single widest
> all 0s/1s vector register for all 0s/1s vector uses in the whole function.
> Add a pass to generate a single widest all 0s/1s vector set instruction at
> entry of the near
On Mon, Dec 2, 2024 at 6:27 AM H.J. Lu wrote:
>
> Add pcmpeq splitters to split
>
> (insn 5 3 7 2 (set (reg:V4SI 100)
> (eq:V4SI (reg:V4SI 98)
> (reg:V4SI 98))) 7910 {*sse2_eqv4si3}
> (expr_list:REG_DEAD (reg:V4SI 98)
> (expr_list:REG_EQUAL (eq:V4SI (const_vector:V
Applied to trunk, thank you!
--Philipp.
On Thu, 17 Apr 2025 at 21:51, Jeff Law wrote:
>
>
>
> On 4/8/25 6:12 AM, Konstantinos Eleftheriou wrote:
> > Hi,
> > Just a ping for https://gcc.gnu.org/pipermail/gcc-patches/2025-
> > March/677635.html <https://gcc.g
On 4/8/25 6:12 AM, Konstantinos Eleftheriou wrote:
Hi,
Just a ping for https://gcc.gnu.org/pipermail/gcc-patches/2025-
March/677635.html <https://gcc.gnu.org/pipermail/gcc-patches/2025-
March/677635.html>.
OK for the trunk. I don't think it's worth porting to the release branches.
jeff
From: Jeremy Bettis
This patch addresses an issue in the C preprocessor where incorrect
line number information is generated when processing files with a
large number of lines. The problem arises from improper handling
of location intervals in the line map, particularly when locations
exceed LINE
tree information to get base block alignment") regression.
Ping for:
<https://inbox.sourceware.org/gcc-patches/alpine.deb.2.21.2502251934260.65...@angie.orcam.me.uk/>.
Maciej
with GCC 15.1 in sight... ping on
gcobc wrapper fixes and additions:
https://gcc.gnu.org/pipermail/gcc-patches/2025-April/680218.html
(note: obviously it would be good if -Wall [1] would work (the "global"
PR for -Wall was postponed to GCC16, so possibly add to gcobol as
intermedia
On Wed, Apr 02, 2025 at 03:32:31PM +0200, Jakub Jelinek wrote:
> I'd like to ping the following PowerPC patches:
>
> https://gcc.gnu.org/pipermail/gcc-patches/2025-March/679312.html
> rs6000: Ignore OPTION_MASK_SAVE_TOC_INDIRECT differences in inlining
> decisions [
On Mon, Apr 07, 2025 at 09:30:59AM +0200, Richard Biener wrote:
> On Mon, Apr 7, 2025 at 9:00 AM Simon Sobisch wrote:
> > My question stands on integrating COBOLworx' UAT as-is for now
> > (Copyright is all on FSF; built automatically [it is autoconf, which is
> > a requirement for VCS checkouts],
Hi,
Just a ping for
https://gcc.gnu.org/pipermail/gcc-patches/2025-March/677635.html.
Thanks,
Konstantinos
Hi,
Just a ping for
https://gcc.gnu.org/pipermail/gcc-patches/2025-March/677788.html .
Thanks,
Konstantinos
Hi Iain,
>>> diff --git a/gcc/ginclude/stddef.h b/gcc/ginclude/stddef.h
>>> index 0d53103ce20..bf9c6e609dc 100644
>>> --- a/gcc/ginclude/stddef.h
>>> +++ b/gcc/ginclude/stddef.h
>>> @@ -89,6 +89,17 @@ see the files COPYING3 and COPYING.RUNTIME respectively.
>>> If not, see
>>> #undef _PTRDIFF_T_
Hi Folks
this has more than 2 weeks without comment,
(it is darwin-local)
thanks
Iain
> On 29 Mar 2025, at 15:23, Iain Sandoe wrote:
>
> C++ modules are not really usable on latest Darwin without resolving this,
> thanks
> Iain
>
>> On 23 Mar 2025, at 12:29, Iain Sandoe wrote:
>>
>> From: Ia
On Mon, Apr 7, 2025 at 9:41 AM Simon Sobisch wrote:
>
>
>
> Am 07.04.2025 um 09:30 schrieb Richard Biener:
> > On Mon, Apr 7, 2025 at 9:00 AM Simon Sobisch wrote:
> >>
> >> My question stands on integrating COBOLworx' UAT as-is for now
> >> (Copyright is all on FSF; built automatically [it is aut
Am 07.04.2025 um 09:36 schrieb Jakub Jelinek:
On Mon, Apr 07, 2025 at 09:30:59AM +0200, Richard Biener wrote:
On Mon, Apr 7, 2025 at 9:00 AM Simon Sobisch wrote:
My question stands on integrating COBOLworx' UAT as-is for now
(Copyright is all on FSF; built automatically [it is autoconf, which
Am 07.04.2025 um 09:30 schrieb Richard Biener:
On Mon, Apr 7, 2025 at 9:00 AM Simon Sobisch wrote:
My question stands on integrating COBOLworx' UAT as-is for now
(Copyright is all on FSF; built automatically [it is autoconf, which is
a requirement for VCS checkouts], possibly also hooked in
On Mon, Apr 7, 2025 at 9:00 AM Simon Sobisch wrote:
>
> My question stands on integrating COBOLworx' UAT as-is for now
> (Copyright is all on FSF; built automatically [it is autoconf, which is
> a requirement for VCS checkouts], possibly also hooked into the current
> test target) - with the goal
My question stands on integrating COBOLworx' UAT as-is for now
(Copyright is all on FSF; built automatically [it is autoconf, which is
a requirement for VCS checkouts], possibly also hooked into the current
test target) - with the goal to get rid of UAT later (next GCC version,
not GCC 15).
T
tree information to get base block alignment") regression.
Ping for:
<https://inbox.sourceware.org/gcc-patches/alpine.deb.2.21.2502251934260.65...@angie.orcam.me.uk/>.
Maciej
Ping!
please review.
Thanks & Regards
Jeevitha
On 20/02/25 7:41 pm, jeevitha wrote:
> Hi All,
>
> The following patch has been bootstrapped and regtested on powerpc64le-linux.
>
> Changes to amo.h include the addition of the following load atomic operations:
> Comp
Gentle ping for https://gcc.gnu.org/pipermail/gcc-patches/2025-March/676875.html
gt; From: Iain Sandoe
> Sent: Wednesday, April 2, 2025 14:24
> To: GCC Patches
> Cc: James K. Lowden ; Robert Dubner
>
> Subject: [ping][PATCH] libgcobol: Provide fallbacks for C32
strfromf32/64
> [PR119296].
>
> Hi folks,
> it would be great to reduce the in-flight patc
> -Original Message-
> From: Iain Sandoe
> Sent: Wednesday, April 2, 2025 15:05
> To: Robert Dubner
> Cc: GCC Patches ; James K. Lowden
>
> Subject: Re: [ping][PATCH] libgcobol: Provide fallbacks for C32
> strfromf32/64 [PR119296].
>
>
>
> > On 2 A
red out how to handle our
> joint responsibility.
understood..
>
> Hence delays.
… will try not to hassle too much :)
>
>
>> -Original Message-
>> From: Iain Sandoe
>> Sent: Wednesday, April 2, 2025 14:24
>> To: GCC Patches
>> Cc: James K. Lowden ; Ro
Hi folks,
it would be great to reduce the in-flight patch stack a bit :)
> On 25 Mar 2025, at 16:40, Iain Sandoe wrote:
>
> This is on top of the C++-ify configure and random_r patches.
> Tested on x86_64,aarch64-Linux and x86_64-darwin, OK for trunk?
> thanks
> Iain
>
> --- 8< ---
>
> strfro
Hi!
I'd like to ping the following PowerPC patches:
https://gcc.gnu.org/pipermail/gcc-patches/2025-March/679312.html
rs6000: Ignore OPTION_MASK_SAVE_TOC_INDIRECT differences in inlining decisions
[PR119327]
https://gcc.gnu.org/pipermail/gcc-patches/2025-March/676989.html
target: A
don't emit 100s of warnings for one call
> > if 100s of vars can escape) case where an address of a local var could have
> > escaped to the musttail call. This is less severe, the code doesn't have
> > to be obviously wrong, so the warning is only enabled in -Wextra.
and
> diagnoses at most one (so that we don't emit 100s of warnings for one call
> if 100s of vars can escape) case where an address of a local var could have
> escaped to the musttail call. This is less severe, the code doesn't have
> to be obviously wrong, so the warning is
> I'd like to ping the
> https://gcc.gnu.org/pipermail/gcc-patches/2025-March/679182.html
> patch.
> I know it is quite controversial and if clang wouldn't be the first
> to implement this I'd certainly not go that way; I am willing to change
> the warning option
Hi folks
> On 24 Mar 2025, at 17:15, Iain Sandoe wrote:
>
>> On 24 Mar 2025, at 16:41, Iain Sandoe wrote:
>>> On 24 Mar 2025, at 16:38, Robert Dubner wrote:
>>>
>>> How about you create the new patch and just edit out the regenerated
>>> configure before sending the e-mail? Typing "autorecon
Hi!
I'd like to ping the
https://gcc.gnu.org/pipermail/gcc-patches/2025-March/678863.html
patch.
Thanks.
On Sat, Mar 22, 2025 at 01:33:51AM +0100, Jakub Jelinek wrote:
> The libcpp left shift handling implements (partially) the C99-C23
> wording where shifts are UB if shift count
I realise this is probably not #1 priority - but it would be nice to have in
gcc-15.
thanks
iain
> On 22 Mar 2025, at 14:31, Iain Sandoe wrote:
>
> 0. Sorry this has taken some time to close off; partly because of waiting
> for input, but mostly that I've been stretched with other work.
> 1.
tree information to get base block alignment") regression.
Ping for:
<https://inbox.sourceware.org/gcc-patches/alpine.deb.2.21.2502251934260.65...@angie.orcam.me.uk/>.
Maciej
On Sat, 22 Mar 2025, Maciej W. Rozycki wrote:
> > This is v3 of the series comprising the final 4 outstanding changes. I
> > note that the corresponding v2 patches have been approved, but concerns
> > were discussed, which this update has addressed.
>
&
C++ modules are not really usable on latest Darwin without resolving this,
thanks
Iain
> On 23 Mar 2025, at 12:29, Iain Sandoe wrote:
>
> From: Iain Sandoe
>
> Tested on x86_64/aarch64 Darwin and x86_64-linux,
> OK for trunk?
> backports to branches supporting modules?
> thanks
> Iain
>
> ---
this (or an alternate implementation) is needed for the cobol FE to build on
darwin,
> On 21 Mar 2025, at 10:00, Iain Sandoe wrote:
>
> It seems that libiberty already has replacements for most of the
> mem* functions, but they are not published via include/libiberty.h.
>
> Tested on x86_64 Li
Hello-
May I please ping this patch? Thanks!
https://gcc.gnu.org/pipermail/gcc-patches/2025-February/675645.html
-Lewis
On Wed, Feb 12, 2025 at 8:27 PM Lewis Hyatt wrote:
>
> Hello-
>
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118838
>
> This patch addresses the issue m
Ping.
Excerpts from Iain Buclaw's message of März 3, 2025 11:14 pm:
> Hi,
>
> This patch implements STAGE1_GDCFLAGS and others to the configure
> machinery, allowing the GDCFLAGS for each bootstrap stage of building
> gdc to be overriden, as is the case with CXXFLAGS
On Tue, 11 Mar 2025, Maciej W. Rozycki wrote:
> This is v3 of the series comprising the final 4 outstanding changes. I
> note that the corresponding v2 patches have been approved, but concerns
> were discussed, which this update has addressed.
Ping for:
<https://inbox.source
tree information to get base block alignment") regression.
Ping for:
<https://inbox.sourceware.org/gcc-patches/alpine.deb.2.21.2502251934260.65...@angie.orcam.me.uk/>.
Maciej
Ping!
please review.
Thanks & Regards
Jeevitha
On 20/02/25 7:41 pm, jeevitha wrote:
> Hi All,
>
> The following patch has been bootstrapped and regtested on powerpc64le-linux.
>
> Changes to amo.h include the addition of the following load atomic operations:
> Comp
Ping.
On 3/5/25 20:21, Jørgen Kvalsvik wrote:
Ping.
On 2/21/25 19:15, Jørgen Kvalsvik wrote:
Ping
On 2/12/25 16:30, Jørgen Kvalsvik wrote:
I have applied fixes for everything in the last review, plus some GNU
style fixes that I had missed previously. We have tested and used a
build with
On Wed, 19 Mar 2025 at 13:09, Jonathan Wakely wrote:
>
> On Sat, 1 Mar 2025 at 05:24, XU Kailiang wrote:
> >
> > Formatting a time point with %c was implemented by calling
> > std::vprint_to with format string constructed from locale's D_T_FMT
> > string, but in some locales this string does not
Gentle ping for https://gcc.gnu.org/pipermail/gcc-patches/2025-March/676875.html
On Wed, 19 Mar 2025 at 13:09, Jonathan Wakely wrote:
>
> On Sat, 1 Mar 2025 at 05:24, XU Kailiang wrote:
> >
> > Formatting a time point with %c was implemented by calling
> > std::vprint_to with format string constructed from locale's D_T_FMT
> > string, but in some locales this string does not
On Sat, 1 Mar 2025 at 05:24, XU Kailiang wrote:
>
> Formatting a time point with %c was implemented by calling
> std::vprint_to with format string constructed from locale's D_T_FMT
> string, but in some locales this string does not compliant to
> chrono-specs. So just use _M_locale_fmt to avoid th
h x86_64-linux -> powerpc64le-linux cross, ok for trunk?
>
> 2025-03-06 Jakub Jelinek
>
> PR target/117207
> PR target/103515
> * gcc.target/powerpc/pr103515.c: Add -fno-tree-vectorize to
> dg-options.
I'd like to ping this patch.
else if (!odr_use && decl_constant_var_p (decl))
>>>>> return decl;
>>>>
>>>> is_constant_capture_proxy might be useful here. And/or a new
>>>> strip_normal_capture function (that I'm surprised doesn't exist yet).
>>> Yeah, that makes a lot of sense, thanks. This is what the attached updated
>>> patch does, successfully tested on x86_64-pc-linux-gnu. OK for trunk?
>>
>>> @@ -4601,7 +4599,7 @@ process_outer_var_ref (tree decl, tsubst_flags_t
>>> complain, bool odr_use)
>>>/* Only an odr-use of an outer automatic variable causes an
>>> error, and a constant variable can decay to a prvalue
>>> constant without odr-use. So don't complain yet. */
>>> - else if (!odr_use && decl_constant_var_p (decl))
>>> + else if (!odr_use && decl_constant_var_p (strip_normal_capture_proxy
>>> (decl)))
>>> return decl;
>>
>> We also want to strip the proxy from the return value.
> Doh, of course, sorry for overlooking this :-/ I checked if I could come up
> with a test case that would fail with this mistake but failed to.
>
> Anyway, I attach another revision that fixes the issue, and was successfully
> tested on x86_64-pc-linux-gnu. OK for trunk?
Friendly ping.
Thanks, Simon
PING!
On Thu, 20 Feb 2025 10:54:30 +0100
Andre Vehreschild wrote:
> Hi all,
>
> attached patch makes an attempt to announce the ABI-changes in the coarrays
> library. Me being German always has difficulties to find a proper wording. So
> please propose improvements.
>
> St
On 3/10/25 9:57 AM, Jerry D wrote:
On 3/10/25 1:08 AM, Andre Vehreschild wrote:
Hi Steve and Jerry,
thanks for the review and the proposed changes. I have based on them, but
needed to adapt some places, because the meaning was changed. Can you
please
take another look?
Jerry, where do I find
On 3/10/25 1:08 AM, Andre Vehreschild wrote:
Hi Steve and Jerry,
thanks for the review and the proposed changes. I have based on them, but
needed to adapt some places, because the meaning was changed. Can you please
take another look?
Jerry, where do I find this check-script? In bin/ nothing ju
tree information to get base block alignment") regression.
Ping for:
<https://inbox.sourceware.org/gcc-patches/alpine.deb.2.21.2502251934260.65...@angie.orcam.me.uk/>.
Maciej
build a STRING_CST
> on the module writing side because that would mean another large
> allocation and copying of the large data.
> RAW_DATA_CST with RAW_DATA_OWNER then needs to be streamed out and in
> by streaming the owner and offset from owner's data and length.
I'd like
On 11-03-2025 15:30, Jonathan Wakely 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.
On 03/03/25 03:05 -0800, yash.shi...@windriver.com wrote:
From: Yash Shinde
This
On 03/03/25 03:05 -0800, yash.shi...@windriver.com wrote:
From: Yash Shinde
This patch addresses an issue in the C preprocessor where incorrect line number
information is generated when processing
files with a large number of lines. The problem arises from improper handling
of location interv
Hi Jerry,
thanks for the review. Committed as 87c7db8b1b2c1484d6de3331098669735d33f95e.
I also had it checked using the W3C validator w/o any errors. Therefore
committed.
Thanks again,
Andre
On Mon, 10 Mar 2025 10:01:46 -0700
Jerry D wrote:
> On 3/10/25 9:57 AM, Jerry D wrote:
> > On
在 2025/3/10 下午3:24, Zhou Zhao 写道:
Ping
Hi,
You need to send another patch for version V2 with modifications.
However, I am currently testing the value of align, and GCC15 is already
in stage 4,
so this patch might have to wait until the GCC16 stage 1 phase before it
can be integrated
Hi Steve and Jerry,
thanks for the review and the proposed changes. I have based on them, but
needed to adapt some places, because the meaning was changed. Can you please
take another look?
Jerry, where do I find this check-script? In bin/ nothing jumps out at me to be
a check-script.
Thanks,
Ping
在 2025/1/7 下午8:45, Zhou Zhao 写道:
在 2025/1/7 下午7:49, Lulu Cheng 写道:
在 2025/1/2 下午5:46, Zhou Zhao 写道:
If SImode reg is continuous left shifted twice, combine related
instruction to one.
gcc/ChangeLog:
* config/loongarch/loongarch.md (extsv_ashlsi3):
New template
Hi, zhaozhou
Ping.
this patch: https://gcc.gnu.org/pipermail/gcc-patches/2025-February/675242.html
series: https://gcc.gnu.org/pipermail/gcc-patches/2025-February/675241.html
On 2/6/25 11:54, David Faust wrote:
> Add two new c-family attributes, "btf_type_tag" and "btf_decl_tag"
Ping.
Patches 3-5 in the series have been reviewed, but depend heavily upon
the DWARF implementation in this patch.
It would be useful to have some indication of whether the new DWARF
implementation is generally OK...
Richard, your feedback on earlier iterations was very helpful, maybe
you
On 3/6/25 10:02 AM, Steve Kargl wrote:
Andre,
Here's a bit of wordsmith. I removed the abbreviation "Esp."
I'm not sure if there is additional markup needed; especially,
with the "-fcoarray=single" I inserted.
Coarray support has been reworked to allow access to components
in derived typ
43PM +0100, Andre Vehreschild wrote:
> PING!
>
> On Thu, 20 Feb 2025 10:54:30 +0100
> Andre Vehreschild wrote:
>
> > Hi all,
> >
> > attached patch makes an attempt to announce the ABI-changes in the coarrays
> > library. Me being German always has diff
Ping.
On 2/12/25 19:00, Jørgen Kvalsvik wrote:
Ping.
On 1/31/25 10:35, Jørgen Kvalsvik wrote:
Record basic blocks that make up a conditional expression with
-fcondition-coverage and report when using the gcov -w/--verbose flag.
This makes the report more accurate when basic blocks are
Ping.
On 2/21/25 19:15, Jørgen Kvalsvik wrote:
Ping
On 2/12/25 16:30, Jørgen Kvalsvik wrote:
I have applied fixes for everything in the last review, plus some GNU
style fixes that I had missed previously. We have tested and used a
build with this applied for 3-4 months now and haven'
On Sat, 1 Mar 2025 at 05:19, XU Kailiang wrote:
>
> Hello libstdc++ maintainers,
>
> I sent a patch in January, but as it was my first patch, my email client
> was not properly configured so the patch format was broken. So I am
> re-sending it now.
>
> https://gcc.gnu.org/pipermail/gcc-patches/202
t; mark_lvalue_use, not mark_rvalue_use (I might very weel be overseeing
> things, and feedback is more than welcome).
>
> This is what the patch does, successfully tested on
> x86_64-pc-linux-gnu.
Friendly ping.
Thanks! Simon
> PR c++/117504
>
> gcc/cp/ChangeLog:
turn the
> outer
> proxy if it finds any.
>
> Successfully tested on x86_64-pc-linux-gnu.
Friendly ping.
Thanks! Simon
> PR c++/110584
>
> gcc/cp/ChangeLog:
>
> * semantics.cc (process_outer_var_ref): Use capture from
> enclosing lambda, if any.
>
ert via
> r11-7266-g24bf79f1798ad1).
>
> Successfully tested on x86_64-pc-linux-gnu.
Friendly ping.
Thanks! Simon
> PR c++/116740
>
> gcc/cp/ChangeLog:
>
> * name-lookup.cc (set_identifier_type_value_with_scope): Don't
> fail assert with ill-fo
Hi!
I'd like to ping the
https://gcc.gnu.org/pipermail/gcc-patches/2025-February/675704.html
and
https://gcc.gnu.org/pipermail/gcc-patches/2025-February/675765.html
patches (both for PR117178, -Wunterminated-string-initialization
regressions and attempts to mitigate it).
Thanks.
Jakub
> The following patch fixes it for the POINTER/REFERENCE_TYPE and
> ARRAY_TYPE cases, but perhaps we need to do the same also for other
> types (INTEGER_TYPE/REAL_TYPE and the like). I guess I'll need to
> construct more testcases.
I'd like to ping the
https://gcc.gnu.org/pi
From: Yash Shinde
This patch addresses an issue in the C preprocessor where incorrect line number
information is generated when processing
files with a large number of lines. The problem arises from improper handling
of location intervals in the line map,
particularly when locations exceed LINE
Formatting a time point with %c was implemented by calling
std::vprint_to with format string constructed from locale's D_T_FMT
string, but in some locales this string does not compliant to
chrono-specs. So just use _M_locale_fmt to avoid this problem.
libstdc++-v3/ChangeLog:
PR libstdc++/
Hello libstdc++ maintainers,
I sent a patch in January, but as it was my first patch, my email client
was not properly configured so the patch format was broken. So I am
re-sending it now.
https://gcc.gnu.org/pipermail/gcc-patches/2025-January/674531.html
Since I do not have commit access, if yo
On 2/26/25 5:58 PM, Jerry D wrote:
This attached patch is intended to clarify the '-x' option using '-x
f77' as an example. I was not sure who should review.
Tested by inspecting the generated info file from make info.
OK for trunk and backport to 14?
Regards,
Jerry
Author: Jerry DeLisle
D
Gentle ping for
https://gcc.gnu.org/pipermail/gcc-patches/2025-February/675450.html
I would like to ping for the following patch that fixes P1 regression:
gcc/ChangeLog:
* combine.cc (distribute_notes) : Remove
REG_UNUSED note from i2 when the register is also mentioned in i3.
gcc/testsuite/ChangeLog:
* gcc.target/i386/pr118739.c: New test.
https://gcc.gnu.org
Ping
On 2/12/25 16:30, Jørgen Kvalsvik wrote:
I have applied fixes for everything in the last review, plus some GNU
style fixes that I had missed previously. We have tested and used a
build with this applied for 3-4 months now and haven't run into any
issues.
Jørgen Kvalsvik (2):
Gentle ping for this series.
https://gcc.gnu.org/pipermail/gcc-patches/2025-February/675241.html
On 2/6/25 11:54, David Faust wrote:
> [v1: https://gcc.gnu.org/pipermail/gcc-patches/2024-October/666911.html
> Changes from v1:
> - Fix a bug in v1 related to generating DWARF for
c4 on LoongArch.
---
Ok for trunk?
Ping.
LGTM!
Thanks.
gcc/testsuite/c-c++-common/toplevel-asm-1.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/gcc/testsuite/c-c++-common/toplevel-asm-1.c
b/gcc/testsuite/c-c++-common/toplevel-asm-1.c
index d6766b00e72..e1687d28e0b 1
h.
> ---
>
> Ok for trunk?
Ping.
> gcc/testsuite/c-c++-common/toplevel-asm-1.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/gcc/testsuite/c-c++-common/toplevel-asm-1.c
> b/gcc/testsuite/c-c++-common/toplevel-asm-1.c
> index d6766b00e72..
On 2/17/25 4:33 AM, Richard Sandiford wrote:
Ping
Feel through the cracks. We really should acknowledge that you know
this code better than anyone and shouldn't need to wait on review.
Anyway, LGTM.
jeff
Hi,
you may want to Cc Lewis Hyatt on such patches (adding him now), I didn't touch
this area.
Alexander
On Mon, 17 Feb 2025, yash.shi...@windriver.com wrote:
> From: Yash Shinde
>
> This patch addresses an issue in the C preprocessor where incorrect line
> number information is generated wh
Ping
Richard Sandiford writes:
> gcc.target/aarch64/pr108840.c has failed since r15-268-g9dbff9c05520
> (which means that I really ought to have looked at it earlier).
>
> The test wants us to fold an SImode AND into all shifts that use it.
> This is something that late-combine is
From: Yash Shinde
This patch addresses an issue in the C preprocessor where incorrect line number
information is generated when processing
files with a large number of lines. The problem arises from improper handling
of location intervals in the line map,
particularly when locations exceed LINE
From: Yash Shinde
This patch addresses an issue in the C preprocessor where incorrect line number
information is generated when processing
files with a large number of lines. The problem arises from improper handling
of location intervals in the line map,
particularly when locations exceed LINE
gt; On Fri, Dec 06, 2024 at 05:07:40PM +0100, Jakub Jelinek wrote:
> > > > > I'd like to ping the
> > > > > https://gcc.gnu.org/pipermail/gcc-patches/2024-November/668699.html
> > > > > patch.
> > > > >
> > > > > The p
Ping.
I have incorporated review comments from Peter in this revised patch. The
comment was to remove -mvsx option from dg-options as this is implied by
-mcpu=power8.
Ok for trunk?
Regards,
Surya
On 09/01/25 8:53 pm, Surya Kumari Jangala wrote:
> Ping
>
> On 02/12/24 2:20 pm, Sur
Ping patch to fix PR target/117251, Add PowerPC XXEVAL support for fusion
optimization in power10
Note, I will be away on vacation from Tuesday February 25th through Friday
March 7th. At this point of time, I do not anticipate bringing a laptop that I
can respond to emails on this account
Ping patches for adding intial dense math support to a potential future PowerPC
processor:
Note, I will be away on vacation from Tuesday February 25th through Friday
March 7th. At this point of time, I do not anticipate bringing a laptop that I
can respond to emails on this account.
Explation
1 - 100 of 1736 matches
Mail list logo
