PING³ – Re: PING³ — Re: PING (and v2) – [Patch] nvptx/nvptx.opt: Update -march-map= for newer sm_xxx

PING³ June 2, 2025 Tobias Burnus wrote: Tobias Burnus wrote: PING² On May 12, 2025, Tobias Burnus wrote: PING. There is actually a minor update as meanwhile CUDA 12.8 was released that added the 'f' suffix and sm_103 and sm_121. Still, the pattern remains the same; hence, a normal PING. On

Re: [PATCH] x86: Update -mtune=intel for Diamond Rapids/Clearwater Forest

On Wed, Jun 25, 2025 at 1:06 PM H.J. Lu wrote: > > -mtune=intel is used to generate a single binary to run well on both big > core and small core, similar to hybrid CPUs. Update -mtune=intel to tune > for Diamond Rapids and Clearwater Forest, instead of Silvermont. > > PR target/120815 > * common

Re: [PATCH, 1 of 4] Add -mcpu=future support for PowerPC

On Mon, Jun 23, 2025 at 07:30:51PM +0530, Surya Kumari Jangala wrote: > Hi Mike, > > On 14/06/25 2:07 pm, Michael Meissner wrote: > > This is patch #1 of 4 that adds the support that can be used in developing > > GCC > > support for future PowerPC processors. > > Please reword the commit message

Re: [AutoFDO] Fix get_original_name to strip only names that are generated after auto-profile

> > > > With part suffixes we also may want to merge specially, since the > > entry_count of the split part does not correspond to entry_count of the > > original function. > > > > I wonder, does partitioned function work with the google tool? I > > remember it had limitations in this respect. >

Re: [PATCH v6 2/3] Use the counted_by attribute of pointers in builtinin-object-size.

On Mon, Jun 23, 2025 at 4:44 PM Qing Zhao wrote: > > gcc/ChangeLog: > > * tree-object-size.cc (access_with_size_object_size): Update comments > for pointers with .ACCESS_WITH_SIZE. > (collect_object_sizes_for): Propagate size info through GIMPLE_ASSIGN > for pointer

Re: [PATCH] gcc: remove atan from edom_only_function

On Mon, Jun 23, 2025 at 6:19 PM Yuao Ma wrote: > > Hi all, > > This patch addresses previous review feedback by splitting the atan handling > into a separate patch. > This patch is part of > https://gcc.gnu.org/pipermail/fortran/attachments/20250607/4a4a9cb6/attachment.obj > > Please take a look

Re: Do not drop discriminator when inlining

> > That is why I checked for loc != UNKNOWN_LOCATION. I did not expect > > UNKNOWN_LOCATION to have discriminators. What they are good for? > > I have no idea, this was simply a defensive review where it's no > longer obvious that inlined_function_outer_scope_p would still work > in all cases.

Re: [PATCH] Don't duplicate setup code cost when do group-candidate cost calucalution.

On Tue, Jun 24, 2025 at 4:39 AM liuhongt wrote: > > From: "hongtao.liu" > > - /* Uses in a group can share setup code, so only add setup cost once. */ > - cost -= cost.scratch; > > It looks like the original code took into account avoiding double > counting, but unfortunately cost is reset ins

Re: [to-be-committed][RISC-V][PR target/118734] Make using zero-strided loads a uarch tunable

> Use pr115763-2.c as example: > > ; w/o this patch, one vec load > fsh fa0,14(sp) > addi a5,sp,14 > vsetivli zero,2,e16,mf4,ta,ma > vlse16.v v1,0(a5),zero > > vs > > ; w/ this patch, two vector instruction > fcvt.s.hfa0,fa0 > vsetivlizero,2,e32,mf2,ta,ma > vfmv.v.fv1,fa0 >

Re: [PATCH, 3 of 4] Add -mcpu=future tests

Hi Mike, On 14/06/25 2:11 pm, Michael Meissner wrote: > This is patch #3 of 4 to add -mcpu=future support to the PowerPC. > > This patch adds simple tests for -mcpu=future. > > I have tested these patches on both big endian and little endian PowerPC > servers, with no regressions. Can I check t

Re: [PATCH 3/3] Assert finished vectorizer pattern COND_EXPR transition

On Tue, 24 Jun 2025, Martin Jambor wrote: > Hi, > > On Fri, Oct 25 2024, Richard Biener wrote: > > The following places a few strathegic asserts so we do not end up > > with COND_EXPRs with a comparison as the first operand during > > vectorization. > > > > Bootstrap and regtest running on x86_64

[PATCH] libstdc++: Report compilation error on formatting "%d" from month_last [PR120650]

For month_day we incorrectly reported day information to be available, which lead to format_error being thrown from the call to formatter::format at runtime, instead of making call to format ill-formed. The included test cover most of the combinations of _ChronoParts and format specifiers. libs

[PATCH] s390: Add some missing vector patterns.

Some patterns that are detected by the autovectorizer can be supported by s390. Add expanders such that autovectorization of these patterns works. Bootstrapped and regtested on s390. Ok for trunk? gcc/ChangeLog: * config/s390/vector.md (avg3_ceil): New pattern. (uavg3_ceil): Ne

[PATCH] cobol: Fix build on 32-bit Darwin [PR120621]

Bootstrapping trunk with 32-bit-default on Mac OS X 10.11 (i386-apple-darwin15) fails: /vol/gcc/src/hg/master/local/gcc/cobol/lexio.cc: In static member function 'static void cdftext::process_file(filespan_t, int, bool)': /vol/gcc/src/hg/master/local/gcc/cobol/lexio.cc:1859:14: error: format '%u'

Re: Do not drop discriminator when inlining

Jan Hubicka writes: >> > That is why I checked for loc != UNKNOWN_LOCATION. I did not expect >> > UNKNOWN_LOCATION to have discriminators. What they are good for? >> >> I have no idea, this was simply a defensive review where it's no >> longer obvious that inlined_function_outer_scope_p would s

RE: [PATCH]middle-end: Fix store_bit_field expansions of vector constructors [PR120718]

On Tue, 24 Jun 2025, Tamar Christina wrote: > > -Original Message- > > From: Richard Biener > > Sent: Tuesday, June 24, 2025 9:58 AM > > To: Tamar Christina > > Cc: gcc-patches@gcc.gnu.org; nd ; Richard Sandiford > > > > Subject: Re: [PATCH]middle-end: Fix store_bit_field expansions of

Re: [PATCH] RISC-V: Add patterns for vector-scalar multiply-(subtract-)accumulate [PR119100]

This LGTM for the trunk. -- Regards Robin

[PATCH] RISC-V: Add Profiles RVA/B23S64 support.

This patch adds support for the RISC-V Profiles RVA23S64 and RVB23S64. gcc/ChangeLog: * common/config/riscv/riscv-common.cc: New Profiles. gcc/testsuite/ChangeLog: * gcc.target/riscv/arch-rva23s.c: New test. * gcc.target/riscv/arch-rvb23s.c: New test. --- gcc/common/co

Re: [PATCH v3] x86: Update memcpy/memset inline strategies for -mtune=generic

On Tue, Jun 24, 2025 at 5:22 AM Hongtao Liu wrote: > > > > Ideall we should catch repeated constants more generally since > > > > this appears elsewhere too. > > > > I am not quite sure where to fit it best. We already have a > > > > machine specific task that loads 0 into

[PATCH V2] testsuite: Fix gcc.target/powerpc/vsx-builtin-7.c test [PR119382]

Hi All, The following patch has been tested on powerpc64le-linux and verified it's fixed. Changes from V1: Added the reason for adding the flag(-fno-ipa-icf) inside the test case. The test vsx-builtin-7.c failed on powerpc64le-linux due to Identical Code Folding (ICF) merging the functions inser

Re: [PATCH]middle-end: Fix store_bit_field expansions of vector constructors [PR120718]

Tamar Christina writes: > store_bit_field_1 has an optimization where if a target is not a memory > operand > and the entire value is being set from something larger we can just wrap a > subreg around the source and emit a move. > > For vector constructors this is however problematic because the

Re: [PATCH, 1 of 4] Add -mcpu=future support for PowerPC

On 24/06/25 10:21 am, Michael Meissner wrote: > On Mon, Jun 23, 2025 at 07:30:51PM +0530, Surya Kumari Jangala wrote: >> Hi Mike, >> >> On 14/06/25 2:07 pm, Michael Meissner wrote: >>> This is patch #1 of 4 that adds the support that can be used in developing >>> GCC >>> support for future Powe

<    1   2