> -Original Message-
> From: Prathamesh Kulkarni
> Sent: 20 December 2024 21:08
> To: Prathamesh Kulkarni ; Tobias Burnus
> ; Joseph Myers
> Cc: Xi Ruoyao ; Matthew Malcomson
> ; gcc-patches@gcc.gnu.org
> Subject: RE: [RFC] PR81358: Enable automatic linking of libatomic
>
>
>
> > ---
David Malcolm writes:
> On Thu, 2025-01-02 at 18:33 +, Joseph Myers wrote:
>> On Thu, 19 Dec 2024, David Malcolm wrote:
>>
>> > Here's an updated version of the patch.
>> >
>> > Changed in v2:
>> > - distinguish between "bool" and "_Bool" when determining
>> > standard version
>> > - more
0001-RISC-V-Add-missing-dg-runtest-to-run-the-testcase-un.patch
Description: Binary data
On Wed, 2025-01-01 at 03:09 +0100, Jose E. Marchesi wrote:
> ---
> gcc/algol68/Make-lang.in | 239 +
> gcc/algol68/README | 102 ++
> gcc/algol68/a68-diagnostics.cc | 450 +
> gcc/algol68/a68-lang.cc | 549 ++
> gcc/algol68/a
Hi,
> It means that we consider that hasher is not perfect, we have several entries
> in the same bucket. Shouldn't we reward those that are spending time on their
> hasher to make it as perfect as possible ?
I don’t think it makes much of a difference for a perfect hashtable as you’re
exiting
Add patchwork configuration, use check_GNU_style.py and git_email.py
to perform prepare and pre-apply checks, disable auto-to-cc preflight
checks as we don't have auto-to-cc script.
It helps with streamlining workflow with b4 so people can use
`b4 prep --check` to check patches before sending or a
Hi all,
This series improved b4 working flow by wire up code style
and changelog checking scripts in b4's automation.
Please help with review and apply.
Thanks!
Signed-off-by: Jiaxun Yang
---
Jiaxun Yang (2):
contrib/gcc-changelog/git_email.py: Rework the script
b4-config: Add usef
Rework the script to align parameters and output with
git_check_commit.py, also better cooperation with b4.
All changes to usage are backward compatible.
contrib/ChangeLog:
* gcc-changelog/git_email.py: (main) Convert to use
argparser; accept file from stdin; Add --verbose
From: xuli
This patch adds testcase for form1, as shown below:
T __attribute__((noinline)) \
sat_s_add_imm_##T##_fmt_1##_##INDEX (T x) \
{\
T sum = (UT)x + (UT)IMM; \
return (x ^ IMM) < 0
From: xuli
This patch would like to support .SAT_ADD when IMM=-1.
Form1:
T __attribute__((noinline)) \
sat_s_add_imm_##T##_fmt_1##_##INDEX (T x) \
{\
T sum = (UT)x + (UT)IMM; \
return (x ^ IMM) < 0
LGTM.
juzhe.zh...@rivai.ai
From: Li Xu
Date: 2025-01-02 16:02
To: gcc-patches
CC: kito.cheng; palmer; juzhe.zhong; pan2.li; xuli
Subject: [PATCH] RISC-V: Add testcases for unsigned imm vec SAT_SUB form2~4
From: xuli
Form2:
void __attribute__((noinline)) \
vec_sat_u_sub_imm##IMM#
Add CC patchworks...@rivosinc.com
Thanks,
Jim
Robin Dapp 於 2025年1月2日 週四 下午3:56寫道：
>
> > Add an extra test case that we do not create a vector store but a scalar
> > store.
>
> LGTM. I haven't seen the patch in the patchworks list or the CI. Would you
> mind sending the same version again CC'i
From: xuli
Form2:
void __attribute__((noinline)) \
vec_sat_u_sub_imm##IMM##_##T##_fmt_2 (T *out, T *in, unsigned limit) \
{ \
unsigned i; \
for (i = 0; i < limit; i++) \
From: xuli
This patch adds testcase for form1, as shown below:
void __attribute__((noinline)) \
vec_sat_s_add_imm_##T##_fmt_1##_##INDEX (T *out, T *op_1, unsigned limit) \
{\
unsigned i;
From: xuli
This patch would like to support vector SAT_ADD when one of the op
is singed IMM.
void __attribute__((noinline)) \
vec_sat_s_add_imm_##T##_fmt_1##_##INDEX (T *out, T *op_1, unsigned limit) \
{
Hi all and happy new year,
I think it makes sense to refer to Newlib 4.5.0 instead of referring
to two specific git commits.
Comments before I commit it?
Actually, due to GCC 15's -std=gnu23, 4.5.0 is recommended
in general as it features:
- fixes for building with gcc-15
besides
- fixe
This testcase came up in a recent LLVM bug report [0] for DSE vs
-ftrivial-auto-var-init=. Add it to our testsuite given that area
could do with better coverage.
[0] https://github.com/llvm/llvm-project/issues/119646
gcc/testsuite/ChangeLog:
* gcc.dg/torture/dse-trivial-auto-var-init.c:
If SImode reg is continuous left shifted twice, combine related
instruction to one.
gcc/ChangeLog:
* config/loongarch/loongarch.md (extsv_ashlsi3):
New template
gcc/testsuite/ChangeLog:
* gcc.target/loongarch/slli-1.c: New test.
---
gcc/config/loongarch/loongarch.md
> Am 02.01.2025 um 10:36 schrieb Jakub Jelinek :
>
> Hi!
>
> In order to stress test RAW_DATA_CST handling, I've tested trunk gcc with
> r15-6339 reapplied and a hack where I've changed
> const unsigned int raw_data_min_len = 128;
> to
> const unsigned int raw_data_min_len = 2;
> in cp_lexe
From: Matthew Malcomson
For the `gcc` and `g++` tools we often pass -B/path/to/object/dir in via
`TEST_ALWAYS_FLAGS` (see e.g. asan.exp where this is set).
In libitm.c++/c++.exp we pass that -B flag via the `tool_flags` argument
to `dg-runtest`.
Passing as the `tool_flags` argument means that th
REGMODE_NATURAL_SIZE is set to 64 bits for everything except
VLA SVE modes. This means that it's possible to modify (say)
the highpart of a TI pseudo or a V2DI pseudo independently
of the lowpart. Modifying such highparts requires a reload
if the highpart ends up in the upper 64 bits of an FPR,
s
Jakub Jelinek writes:
> Hi!
>
> libgdiagnostics/conf.py breaks update-copyright.py --this-year,
> which only accepts copyright year in u'' literals in python files,
> not in ''.
>
> u'' strings is what e.g. libgccjit conf.py uses.
> Tested by building libgdiagnostics docs without/with this patch,
writes:
> From: Matthew Malcomson
>
> For the `gcc` and `g++` tools we often pass -B/path/to/object/dir in via
> `TEST_ALWAYS_FLAGS` (see e.g. asan.exp where this is set).
> In libitm.c++/c++.exp we pass that -B flag via the `tool_flags` argument
> to `dg-runtest`.
>
> Passing as the `tool_flags`
Dear all,
this patch addresses overeager optimization of Cray pointers when
used in comparisons. Cray pointers are non-standard, and odd in a
sense that they were introduced before modern Fortran pointers.
Comparisons with e.g. a "NULL" pointer are actually comparisons
with integer zero etc., whi
> On Wed, 2025-01-01 at 03:09 +0100, Jose E. Marchesi wrote:
>> ---
>> gcc/algol68/Make-lang.in | 239 +
>> gcc/algol68/README | 102 ++
>> gcc/algol68/a68-diagnostics.cc | 450 +
>> gcc/algol68/a68-lang.cc | 549 ++
>> gcc/
On 1/2/25 12:04 PM, Harald Anlauf wrote:
Dear all,
this patch addresses overeager optimization of Cray pointers when
used in comparisons. Cray pointers are non-standard, and odd in a
sense that they were introduced before modern Fortran pointers.
Comparisons with e.g. a "NULL" pointer are actua
When gcc is built for x86_64-linux-musl target, stack unwinding from
within signal handler stops at the innermost signal frame. The reason
for this behaviro is that the signal trampoline is not accompanied with
appropiate CFI directives, and the fallback path in libgcc to recognize
it by the code
From: Svante Signell
GNU/Hurd uses glibc just like GNU/Linux.
This is needed for gcc to notice that glibc supports split stack in
finish_options.
gcc/ChangeLog:
* gcc/config/gnu.h (OPTION_GLIBC_P, OPTION_GLIBC): Define.
Patch from Svante Signell for PR go/104290.
---
gcc/config/gnu.h
On Thu, 2025-01-02 at 13:34 +0100, Jakub Jelinek wrote:
> On Thu, Jan 02, 2025 at 11:51:20AM +, Richard Sandiford wrote:
> > Jakub Jelinek writes:
> > > libgdiagnostics/conf.py breaks update-copyright.py --this-year,
> > > which only accepts copyright year in u'' literals in python
> > > files
On Thu, 2025-01-02 at 10:39 -0500, David Malcolm wrote:
> On Thu, 2025-01-02 at 13:34 +0100, Jakub Jelinek wrote:
> > On Thu, Jan 02, 2025 at 11:51:20AM +, Richard Sandiford wrote:
> > > Jakub Jelinek writes:
> > > > libgdiagnostics/conf.py breaks update-copyright.py --this-year,
> > > > which
On Thu, 2025-01-02 at 18:33 +, Joseph Myers wrote:
> On Thu, 19 Dec 2024, David Malcolm wrote:
>
> > Here's an updated version of the patch.
> >
> > Changed in v2:
> > - distinguish between "bool" and "_Bool" when determining
> > standard version
> > - more test coverage
> >
> > Successful
Tamar Christina writes:
>> >> So I think ideally, we should try to detect whether the indices come
>> >> directly from memory or are the result of arithmetic. In the former case,
>> >> we should do the loads adjustment above. In the latter case, we should
>> >> keep the vec_to_scalar accounting
On Tue, 31 Dec 2024, Sandra Loosemore wrote:
> diff --git a/gcc/fortran/intrinsic.texi b/gcc/fortran/intrinsic.texi
> index d11d37761d9..b47180126ca 100644
> --- a/gcc/fortran/intrinsic.texi
> +++ b/gcc/fortran/intrinsic.texi
> @@ -1577,7 +1577,7 @@ if @var{Y} is present, @var{X} shall be REAL.
>
Hello,
Thiago Jung Bauermann writes:
> This problem was noticed because the recent binutils commit
> d5cbf916be4a ("gas/ELF: also reject merge entity size being zero") caused
> gas to be stricter about mergeable sections without an entity size:
>
> configure:27013: checking assembler for section
> "Jose E. Marchesi" writes:
>
>> This patch contains the changes to files in the GCC top-level
>> directory to introduce the Algol 68 front-end.
>> ---
>> MAINTAINERS |2 +
>> Makefile.def |3 +
>> Makefile.in | 1341 +-
>> Make
On 1/2/25 20:22, Maciej W. Rozycki wrote:
On Tue, 31 Dec 2024, Sandra Loosemore wrote:
diff --git a/gcc/fortran/intrinsic.texi b/gcc/fortran/intrinsic.texi
index d11d37761d9..b47180126ca 100644
--- a/gcc/fortran/intrinsic.texi
+++ b/gcc/fortran/intrinsic.texi
@@ -1577,7 +1577,7 @@ if @var{Y} is
Hi!
In order to stress test RAW_DATA_CST handling, I've tested trunk gcc with
r15-6339 reapplied and a hack where I've changed
const unsigned int raw_data_min_len = 128;
to
const unsigned int raw_data_min_len = 2;
in cp_lexer_new_main and 64 to 4 several times in c_parser_initval
and c_maybe_o
Hi!
When running update-copyright.py --this-year, I've encountered various
failures, this patch works around those.
Committed as obvious.
For gen-evolution.awk, gen-cxxapi-file.py and uname2c.h I've dealt with
copyright year updates manually later on.
Note, I've also rotated ChangeLogs with yea
Hi!
libgdiagnostics/conf.py breaks update-copyright.py --this-year,
which only accepts copyright year in u'' literals in python files,
not in ''.
u'' strings is what e.g. libgccjit conf.py uses.
Tested by building libgdiagnostics docs without/with this patch, the
difference is just the expected a
This patch implements 4 rules for semantics of round func in match.pd under
-funsafe-math-optimizations:
1) (x-floor(x)) < (ceil(x)-x) ? floor(x) : ceil(x) -> floor(x+0.5)
2) (x-floor(x)) >= (ceil(x)-x) ? ceil(x) : floor(x) -> floor(x+0.5)
3) (ceil(x)-x) > (x-floor(x)) ? floor(x) : ceil(x) -> floor
Hi Sandra,
Sandra Loosemore wrote:
After reimplementing late resolution of "declare variant", the
declare_variant_alt and calls_declare_variant_alt flags on struct
cgraph_node are no longer used by anything. For the purposes of
marking functions that need late resolution, the
has_omp_variant_co
On 1/2/25 12:08, Richard Sandiford wrote:
+# This set in order to give libitm.c++/c++.exp a nicely named flag to set
+# when adding C++ options.
+set TEST_ALWAYS_FLAGS ""
This looked odd at first glance. By unconditionally writing "" to the
variable, it seems to subvert the save
Add Reviewer Richard Biener.
> -原始邮件-
> 发件人: "Zhou Zhao"
> 发送时间:2025-01-02 19:37:07 (星期四)
> 收件人: gcc-patches@gcc.gnu.org
> 抄送: xry...@xry111.site, i...@xen0n.name, chengl...@loongson.cn,
> xucheng...@loongson.cn, zhaoz...@loongson.cn
> 主题: [PATCH] match.pd: Fold pattern of round semanti
On Wed, Jan 1, 2025 at 1:44 AM Fangrui Song wrote:
>
> so that
> `gcc -c a.cc --coverage -fprofile-prefix-map=$PWD=.`
> does not emit $PWD in the generated a.gcno file.
This looks OK to me. Please leave a few days for others to comment though.
Thanks,
Richard.
> PR gcov-profile/96092
>
On Thu, Jan 02, 2025 at 11:51:20AM +, Richard Sandiford wrote:
> Jakub Jelinek writes:
> > libgdiagnostics/conf.py breaks update-copyright.py --this-year,
> > which only accepts copyright year in u'' literals in python files,
> > not in ''.
> >
> > u'' strings is what e.g. libgccjit conf.py us
Hi All,
When a target does not support gathers and scatters the vectorizer tries to
emulate these using scalar loads/stores and a reconstruction of vectors from
scalar.
The loads are still marked with VMAT_GATHER_SCATTER to indicate that they are
gather/scatters, however the vectorizer also asks
Tamar Christina writes:
> Hi All,
>
> When a target does not support gathers and scatters the vectorizer tries to
> emulate these using scalar loads/stores and a reconstruction of vectors from
> scalar.
>
> The loads are still marked with VMAT_GATHER_SCATTER to indicate that they are
> gather/scat
Tamar Christina writes:
> Hi All,
>
> The following testcase
>
> #pragma GCC target ("+sve")
> extern char __attribute__ ((simd, const)) fn3 (int, short);
> void test_fn3 (float *a, float *b, double *c, int n)
> {
> for (int i = 0; i < n; ++i)
> a[i] = fn3 (b[i], c[i]);
> }
>
>
> -Original Message-
> From: Richard Sandiford
> Sent: Thursday, January 2, 2025 5:19 PM
> To: Tamar Christina
> Cc: gcc-patches@gcc.gnu.org; nd ; Richard Earnshaw
> ; ktkac...@gcc.gnu.org
> Subject: Re: [PATCH]AArch64: Implement four and eight chunk VLA concats
> [PR118272]
>
> Tamar Ch
The test was failing on x86 because longdouble128 only checks sizeof,
rather than a full 128-bit payload. Using _Float128 is more portable
and still exposes the original bug.
Tested on aarch64-linux-gnu and x86_64-linux-gnu, pushed as obvious.
Richard
gcc/testsuite/
PR target/118184
Tamar Christina writes:
>> > [...]
>> > #define iterations 10
>> > #define LEN_1D 32000
>> >
>> > float a[LEN_1D], b[LEN_1D];
>> >
>> > float
>> > s4115 (int *ip)
>> > {
>> > float sum = 0.;
>> > for (int i = 0; i < LEN_1D; i++)
>> > {
>> > sum += a[i] * b[ip[i]];
>
> -Original Message-
> From: Richard Sandiford
> Sent: Thursday, January 2, 2025 4:52 PM
> To: Tamar Christina
> Cc: gcc-patches@gcc.gnu.org; nd ; Richard Earnshaw
> ; ktkac...@gcc.gnu.org
> Subject: Re: [PATCH]AArch64: Fix costing of emulated gathers/scatters
> [PR118188]
>
> Tamar Chri
This came up in the context of dispatch patching, where the location
was very confusing (pointing to the first letter of the first variable).
The OpenMP variable-list parser has two modes, one is used to directly
parse a clause, in which case a tree node is created with the proper
location. And a
> -Original Message-
> From: Richard Sandiford
> Sent: Thursday, January 2, 2025 5:54 PM
> To: Tamar Christina
> Cc: gcc-patches@gcc.gnu.org; nd ; Richard Earnshaw
> ; ktkac...@gcc.gnu.org
> Subject: Re: [PATCH]AArch64: Fix costing of emulated gathers/scatters
> [PR118188]
>
> Tamar Chri
during RTL pass: reload
../../../../../libstdc++-v3/src/c++20/tzdb.cc: In function ‘std::istream&
std::chrono::{anonymous}::operator>>(std::istream&, at_time&)’:
../../../../../libstdc++-v3/src/c++20/tzdb.cc:2080:5: internal compiler error:
in gen_rtx_SUBREG, at emit-rtl.cc:1032
2080 | }
Support the 'has_device_addr' clause with OpenMP's 'dispatch'
directive.
The testcase is even more questionable as the C/C++ testcase
(looking at it globally/semantically), but it tests (locally)
what it is supposed to test: namely, 'has_device_addr' does not
fulfill the 'is_device_ptr' property
Matthew Malcomson writes:
> On 1/2/25 12:08, Richard Sandiford wrote:
>>> +# This set in order to give libitm.c++/c++.exp a nicely named flag to
>>> set
>>> +# when adding C++ options.
>>> +set TEST_ALWAYS_FLAGS ""
>>
>> This looked odd at first glance. By unconditionally writing ""
On Linux/x86_64,
2b687ad95de61091105d040d6bc06cb3d44ac3d1 is the first bad commit
commit 2b687ad95de61091105d040d6bc06cb3d44ac3d1
Author: Richard Sandiford
Date: Thu Jan 2 11:34:52 2025 +
aarch64: Detect word-level modification in early-ra [PR118184]
caused
FAIL: gcc.dg/torture/pr118
Hi All,
The following testcase
#pragma GCC target ("+sve")
extern char __attribute__ ((simd, const)) fn3 (int, short);
void test_fn3 (float *a, float *b, double *c, int n)
{
for (int i = 0; i < n; ++i)
a[i] = fn3 (b[i], c[i]);
}
at -Ofast ICEs because my previous patch only a
Hi!
The embed-17.C testcase is miscompiled and pr118214.C testcase used to be
miscompiled on the trunk before I've temporarily reverted the
r15-6339 C++ large initializer speed-up commit in r15-6448.
The problem is that reshape_* is only sometimes allowed to modify the given
CONSTRUCTOR in place (
Sandra Loosemore wrote:
[in https://gcc.gnu.org/pipermail/gcc-patches/2024-November/669055.html ]
Presently, the code to handle OpenMP attribute-syntax pragmas in the C
front end assumes nothing else is messing with redirecting
parser->tokens, and makes no provision for restoring it from anythin
On Thu, 19 Dec 2024, David Malcolm wrote:
> Here's an updated version of the patch.
>
> Changed in v2:
> - distinguish between "bool" and "_Bool" when determining
> standard version
> - more test coverage
>
> Successfully bootstrapped & regrtested on x86_64-pc-linux-gnu.
> OK for trunk?
OK.
On Thu, 19 Dec 2024, David Malcolm wrote:
> gcc/c/ChangeLog:
> PR c/118112
> * c-typeck.cc (inform_declaration): Add "function_expr" param and
> use it for cases where we couldn't show the function decl to show
> field decls for callbacks.
> (build_function_call_vec):
> As to where to host the project, the obvious choice is perhaps a
> project at sourceware, but it would be nice if we could develop the
> front-end in a branch in the GCC git repo, to have a mailing list
> under gcc.gnu.org and to use a page in the GCC wiki to track the FE
> progress... please l
On Thu, 19 Dec 2024, Robert Dubner wrote:
> At compile-time (or on the host), we also do numeric calculations. The
> ISO specification allows for compile-time computations specified in the
> source code. In addition, at times I put initial values for the COBOL
> variables into the run-time struc
65 matches
Mail list logo
