* Jeff Law:
> Anyway, this test was the one I was most concerned about. Basically
> we're testing that on a !dfp target that the builtins are not available.
> It expects a warning, but gets an error by default now. I just
> changed the test to use -fpermissive, so that the test behaves as
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112829
Bug ID: 112829
Summary: Dump PGO profiles to a memory buffer
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
Last patch for the night. There's still a bit of minor fallout left in
GCC (loongarch testsuite for example). But things are looking good on
the targets I test. The plan is to start submitting the various
newlib/libgloss fixes tomorrow.
Anyway, this test was the one I was most concerned
read_encoded_value_with_base has an ifdef'd code path conditional on
__FDPIC__ which was calling _Unwind_gnu_Find_got without a prototype.
This naturally caused various build failures.
This adds a suitable prototype.
Pushed to the trunk.
commit 4cef6daf40f4aefd748245a720955d4e52d1a81e
There's a caller/callee type mismatch in this test that shows up on
targets where ints are something other than 32 bit types.
Based on reviewing the original bug report, the fix and the part of the
test this fixes, I'm reasonably confident this hasn't compromised the test.
Pushed to the
I don't remember what port triggered this, but it's obviously that
comp-goto-1.c needs to be fixed.
Basically the test has two implementations. One is just a dummy with no
return value on main() triggering the new errors.
Pushed to the trunk.
Jeffcommit
Similar to others. Where it's easy to fix the implicit types or add
prototypes I did. One was just ugly and I didn't want to think too
hard, so I just added -fpermissive.
Pushed to the trunk.
Jeff
commit 595c695216e72c8491bf20d30e5298e2064caa73
Author: Jeff Law
Date: Sat Dec 2
The nios2 port has two tests that are affected by the recent changes.
In cdx-ldstwm-1.c it was easiest to just add -fpermissive. for
cdx-ldstwm-2.c adding an prototype for exit and abort is all that's needed.
Pushed to the trunk,
Jeff
commit 2280317c3771a28e9288b7f4c4c23aa4b0ac31dd
Author:
The rx port has a bunch of what I presume are ABI compatibility
functions in libgcc. Those compatibility functions routines such as
__eqdf2 from libgcc, but without a prototype. This patch adds the
missing prototypes.
Pushed to the trunk,
Jeff
commit
Two minor regressions on the H8 were triggered by the C99 changes.
First pr58400.c has several functions without prototypes. I just added
-fpermissive to that test. Second pr17306-2.c has a single call to an
unprototyped function for which I added the prototype.
These are both H8 specific
Two issues prevent the frv-elf port from building after the C99 changes.
First the trampoline code emitted into libgcc has calls to exit, but
no prototype. Adding a trivial prototype for exit() into the macro
fixes that little goof.
Second, frvbegin.c has a call to atexit, so a quick
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112789
Xi Ruoyao changed:
What|Removed |Added
CC||xry111 at gcc dot gnu.org
--- Comment #13
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109289
--- Comment #6 from Jan Dubiec ---
(In reply to Florian Weimer from comment #3)
> Jan, do you actually experience a build failure? The part you quoted only
> shows warnings.
Florian, it used to be just the warnings, but now (commit 1461b431) I
On Sun, 2023-12-03 at 00:17 +, Jonny Grant wrote:
> @@ -733,7 +733,7 @@ To configure GCC:
> @smallexample
> % mkdir @var{objdir}
> % cd @var{objdir}
> -% @var{srcdir}/configure [@var{options}] [@var{target}]
> +% ../@var{srcdir}/configure [@var{options}] [@var{target}]
> @end smallexample
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112813
--- Comment #1 from JuzheZhong ---
I think it's probably fixed on the trunk by my recent patch:
https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=923a67f17badcbe6e2b2e5d3570a265443258c8e
If it has been fixed, plz verify it and send a patch with
On Sat, Dec 2, 2023 at 5:40 PM Jonny Grant wrote:
>
> Hello
>
> I held of making a patch to change this (to remove it), does Standardeze mean
> something:
>
> https://gcc.gnu.org/projects/cxx-reflection/index.html
It means written in the same form as the language that is the C++
standard. It
Hello
I held of making a patch to change this (to remove it), does Standardeze mean
something:
https://gcc.gnu.org/projects/cxx-reflection/index.html
Kind regards
Jonny
This implements the OpenMP low-latency memory allocator for AMD GCN using the
small per-team LDS memory (Local Data Store).
Since addresses can now refer to LDS space, the "Global" address space is
no-longer compatible. This patch therefore switches the backend to use
entirely "Flat" addressing
This patch adds support for allocating low-latency ".shared" memory on
NVPTX GPU device, via the omp_low_lat_mem_space and omp_alloc. The memory
can be allocated, reallocated, and freed using a basic but fast algorithm,
is thread safe and the size of the low-latency heap can be configured using
This patch series is a rework of the patch series posted in August.
https://patchwork.sourceware.org/project/gcc/list/?series=23045=%2A=both
The series implements device-specific allocators and adds a low-latency
allocator for both GPUs architectures.
This time the omp_low_lat_mem_alloc does
The NVPTX low latency memory is not accessible outside the team that allocates
it, and therefore should be unavailable for allocators with the access trait
"all". This change means that the omp_low_lat_mem_alloc predefined
allocator no longer works (but omp_cgroup_mem_alloc still does).
2023-12-03 Jonathan Grant
htdocs/
* bugs/management.html: adition spelling.
* codingrationale.html: suprises spelling.
* contribute.html: elipsis leter spelling.
* gcc-14/changes.html: modifed spelling.
* gccmission.html: groundrules spelling.
*
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112789
--- Comment #12 from Andrew Pinski ---
(In reply to Sam James from comment #11)
> (In reply to Andrew Pinski from comment #7)
> > Sounds like that HPC QCD app is broken. You should report it to the
> > developers. Also since __builtin_ctzg is
2023-12-03 Jonathan Grant
gcc/doc
* install.texi: show ../ back from the objdir in the example invoking
configure
correct spelling support, arithmetics
This page is what is generated from install.texi
https://gcc.gnu.org/install/configure.html
>From
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112789
--- Comment #11 from Sam James ---
(In reply to Andrew Pinski from comment #7)
> Sounds like that HPC QCD app is broken. You should report it to the
> developers. Also since __builtin_ctzg is added, adding __builtin_ctzs really
> does not make
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112789
--- Comment #10 from Andrew Pinski ---
(In reply to gnzlbg from comment #8)
> Oh! Sorry! I see this was resolved as WONTFIX.
>
> Does that mean that GCC, in contrast with the LLVM community - which is
> always super helpful and friendly when
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112789
--- Comment #9 from gnzlbg ---
> > Look at that part where __builtin_ctzs is mentioned there.
> It just says it is valid inside a constexpr and nothing else about the
> builtin.
Yes, seems like a bug / pr should be opened in the llvm project
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112789
--- Comment #8 from gnzlbg ---
Oh! Sorry! I see this was resolved as WONTFIX.
Does that mean that GCC, in contrast with the LLVM community - which is always
super helpful and friendly when it comes to trying to enable their toolchains
to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112789
--- Comment #7 from Andrew Pinski ---
(In reply to gnzlbg from comment #6)
> Thanks for all the quick feedback!
>
> > Also clang does not even document __builtin_ctzs anywhere ...
>
> This builtin is documented in the list of clang bultins.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112789
--- Comment #6 from gnzlbg ---
Thanks for all the quick feedback!
> Also clang does not even document __builtin_ctzs anywhere ...
This builtin is documented in the list of clang bultins. You can find it by
using CTRL+F for the builtin, in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112828
Bug ID: 112828
Summary: Abort with malloc(): corrupted top size
Product: gcc
Version: 13.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109289
Andrew Pinski changed:
What|Removed |Added
CC||pinskia at gcc dot gnu.org
--- Comment
On Sat, Dec 02, 2023 at 11:04:04AM +, Richard Sandiford wrote:
> I still maintain that so much stuff relies on the lack of false-positive
> REG_UNUSED notes that (whatever the intention might have been) we need
> to prevent the false positive. Like Andrew says, any use of single_set
> is
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112826
Andrew Pinski changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
Dear GCC community,
I am assigned the task to debug the trees as being produced by the
cp_parser. I was able to print some of the trees using the debug_tree()
function. But I am still confused as to where is the tree object that
corresponds to the translation unit being parsed. There is no such
Snapshot gcc-13-20231202 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/13-20231202/
and on various mirrors, see https://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 13 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
Use std::vector instead of malloc'd pointer
to get automatic freeing of memory.
Result was verified by valgrind, which showed
one less loss record.
I think Jonathan is/was working on this transition
but on a larger scale.
0001-driver-Fix-memory-leak.patch
Description: Binary data
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112825
Gaius Mulley changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
This patch documents the optimization parameter
riscv-strcmp-inline-limit, which can be used to tweak the behaviour
of -minline-strcmp and -minline-strncmp.
gcc/ChangeLog:
PR target/112650
* doc/invoke.texi: Document riscv-strcmp-inline-limit.
Signed-off-by: Christoph Müllner
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112823
Sam James changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
> Am 02.12.2023 um 14:15 schrieb Richard Sandiford :
>
> Eric Botcazou writes:
>>> So sorry to be awkward, but I don't think this is the way to go. I think
>>> we'll just end up playing whack-a-mole and adding df_note_add_problem to
>>> lots of passes.
>>
>> We have doing that for the past
On Fri, Nov 3, 2023 at 8:37 AM Szabolcs Nagy wrote:
>
> gcc/testsuite/ChangeLog:
>
> * gcc.target/aarch64/eh_return-2.c: New test.
> * gcc.target/aarch64/eh_return-3.c: New test.
gcc.target/aarch64/eh_return-3.c fails when running the testsuite with
`-march=armv9-a+sve` . I
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112406
--- Comment #24 from Andrew Pinski ---
(In reply to GCC Commits from comment #22)
> gcc/testsuite/ChangeLog:
>
> * gcc.target/aarch64/pr112406-2.c: New test.
This testcase now fails after the recent changes to make some
Calling the driver::finalize() method before returning from main
seems to be reducing some memory leaks of the driver (PR93019).
$ head -n20 before_patch.txt
==385521== Memcheck, a memory error detector
==385521== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==385521== Using
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112827
Andrew Pinski changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
-checking=yes --prefix=/local/suz-local/software/local/gcc-trunk
--enable-sanitizers --enable-languages=c,c++ --disable-werror --enable-multilib
Thread model: posix
Supported LTO compression algorithms: zlib
gcc version 14.0.0 20231202 (experimental) (GCC)
[508] %
[508] % gcctk -O1 small.c
during
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112822
Peter Bergner changed:
What|Removed |Added
Last reconfirmed||2023-12-02
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112826
Xi Ruoyao changed:
What|Removed |Added
Resolution|--- |INVALID
Status|UNCONFIRMED
contrib/ChangeLog:
* download_prerequisites
: Parse --only-gettext.
(echo_archives): Check only_gettext and stop early if true.
(helptext): Document --only-gettext.
---
Afternoon,
This patch adds a --only-gettext option to download_prerequisites for
when the only
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112826
Arsen Arsenović changed:
What|Removed |Added
CC||arsen at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112826
Bug ID: 112826
Summary: gcc rejects the valid code and reports undefined
reference
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
On 12/1/23 22:47, Sam James wrote:
Jeff Law writes:
On 12/1/23 18:13, Sam James wrote:
钟居哲 writes:
Hi, This patch cause error on building newlib/glibc/musl on RISC-V port:
On 12/1/23 20:31, waffl3x wrote:
On Friday, December 1st, 2023 at 9:52 AM, Jason Merrill
wrote:
On 12/1/23 01:02, waffl3x wrote:
I ran into another issue while devising tests for redeclarations of
xobj member functions as static member functions and vice versa. I am
pretty sure by the
This fixes issues reported by David Edelsohn , and by
Eric Gallager .
ChangeLog:
* Makefile.def (gettext): Disable (via missing)
{install-,}{pdf,html,info,dvi} and TAGS targets. Set no_install
to true. Add --disable-threads --disable-libasprintf. Drop the
Richard Biener writes:
> On Thu, Sep 7, 2023 at 11:30 AM Richard Sandiford via Gcc-patches
> wrote:
>>
>> When I tried to use config-list.mk, the build for every triple except
>> the build machine's failed for m2. This is because, unlike other
>> languages, m2 builds target objects during
Christophe Lyon writes:
> Hi!
>
>
> On Thu, 7 Sept 2023 at 11:30, Richard Sandiford via Gcc-patches <
> gcc-patches@gcc.gnu.org> wrote:
>
>> When I tried to use config-list.mk, the build for every triple except
>> the build machine's failed for m2. This is because, unlike other
>> languages, m2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112825
Bug ID: 112825
Summary: Modula 2 builds target objects as part of all-gcc
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112772
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Resolution|--- |FIXED
Keywords|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93762
--- Comment #5 from GCC Commits ---
The master branch has been updated by Harald Anlauf :
https://gcc.gnu.org/g:27ce74fa23c93c1189c301993cd19ea766e6bdb5
commit r14-6081-g27ce74fa23c93c1189c301993cd19ea766e6bdb5
Author: Harald Anlauf
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100651
--- Comment #16 from GCC Commits ---
The master branch has been updated by Harald Anlauf :
https://gcc.gnu.org/g:27ce74fa23c93c1189c301993cd19ea766e6bdb5
commit r14-6081-g27ce74fa23c93c1189c301993cd19ea766e6bdb5
Author: Harald Anlauf
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110734
--- Comment #20 from Julian Waters ---
cppreference at least seems to indicate it retroactively applies to C++11
https://en.cppreference.com/w/cpp/language/asm
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112794
Jason Merrill changed:
What|Removed |Added
Last reconfirmed||2023-12-02
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112743
JuzheZhong changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
On Sat, 2023-12-02 at 20:44 +0800, chenglulu wrote:
> > > @@ -657,12 +658,18 @@ abi_str (struct loongarch_abi abi)
> > > strlen (loongarch_abi_base_strings[abi.base]));
> > > else
> > > {
> > > + /* This situation has not yet occurred, so in order to avoid
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112824
--- Comment #1 from Chris Elrod ---
Here I have added a godbolt example where I manually unroll the array, where
GCC generates excellent code https://godbolt.org/z/sd4bhGW7e
I'm not sure it is 100% optimal, but with an inner Dual size of `7`,
Eric Botcazou writes:
>> So sorry to be awkward, but I don't think this is the way to go. I think
>> we'll just end up playing whack-a-mole and adding df_note_add_problem to
>> lots of passes.
>
> We have doing that for the past 15 years though, so what has changed?
Off-hand, I couldn't
在 2023/12/2 下午6:15, Xi Ruoyao 写道:
On Sat, 2023-12-02 at 16:14 +0800, Lulu Cheng wrote:
/* snip */
diff --git a/gcc/config/loongarch/loongarch-opts.cc
b/gcc/config/loongarch/loongarch-opts.cc
index b5836f198c0..6861642a98d 100644
--- a/gcc/config/loongarch/loongarch-opts.cc
+++
Some targets do not provide a prototype for fork, and compilation now
fails with an implicit-function-declaration error.
libgcc/
* libgcov-interface.c (__gcov_fork):
Generated code is the same on x86_64-linux-gnu. Okay for trunk?
Thanks,
Florian
---
libgcc/libgcov-interface.c | 2 +-
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112820
Nathaniel Shead changed:
What|Removed |Added
CC||nathanieloshead at gmail dot
com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109289
--- Comment #4 from Florian Weimer ---
What I can I do here to help? What's an easy emutls target to build?
> So sorry to be awkward, but I don't think this is the way to go. I think
> we'll just end up playing whack-a-mole and adding df_note_add_problem to
> lots of passes.
We have doing that for the past 15 years though, so what has changed?
> (FTR, I'm not saying passes have to avoid false
Correct a spelling mistake this page:
https://gcc.gnu.org/contribute.html
>From 5bfcc97cafb195c68d3110247dabeaf464b8d367 Mon Sep 17 00:00:00 2001
From: Jonathan Grant
Date: Sat, 2 Dec 2023 11:55:40 +
Subject: [PATCH] htdocs/contribute.html: correct disctinct->distinct spelling
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112824
Bug ID: 112824
Summary: Stack spills and vector splitting with vector builtins
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
> Am 02.12.2023 um 12:05 schrieb Jakub Jelinek :
>
> Hi!
>
> lower_addsub_overflow uses handle_cast or handle_operand to extract current
> limb from the operands. Both of those functions heavily assume that they
> return a large or huge BITINT_TYPE. The problem in the testcase is that
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60994
--- Comment #19 from GCC Commits ---
The master branch has been updated by Roger Sayle :
https://gcc.gnu.org/g:193ef02a7f4f3e5349ad9cf8d3d4df466a99b677
commit r14-6075-g193ef02a7f4f3e5349ad9cf8d3d4df466a99b677
Author: Roger Sayle
Date: Sat
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112743
--- Comment #6 from Li Pan ---
Double confirmed the riscv-gnu-toolchain can be built successfully with the
latest newlib.
Hi!
lower_addsub_overflow uses handle_cast or handle_operand to extract current
limb from the operands. Both of those functions heavily assume that they
return a large or huge BITINT_TYPE. The problem in the testcase is that
this is violated. Normally, lower_addsub_overflow isn't even called
Jakub Jelinek writes:
> Hi!
>
> The following testcase ICEs on x86_64-linux since df_note_add_problem ()
> call has been added to mode switching.
> The problem is that the pro_and_epilogue pass in
> prepare_shrink_wrap -> copyprop_hardreg_forward_bb_without_debug_insn
> uses regcprop.cc
Hi!
foo in the unroll-5.C testcase ICEs because cp_parser_pragma_unroll
during parsing calls maybe_constant_value unconditionally, which is
fine if !processing_template_decl, but can ICE otherwise.
While just calling fold_non_dependent_expr there instead could be enough
to fix the ICE (and I
Hi!
The following testcase ICEs on x86_64-linux since df_note_add_problem ()
call has been added to mode switching.
The problem is that the pro_and_epilogue pass in
prepare_shrink_wrap -> copyprop_hardreg_forward_bb_without_debug_insn
uses regcprop.cc infrastructure which relies on accurate
> On 2 Dec 2023, at 09:42, Martin Uecker wrote:
>
>
>> Bootstrapped/regtested on x86_64-pc-linux-gnu, ok for trunk?
>>
>> -- >8 --
>> It came up that a good hardening strategy is to disable trampolines
>> which may require executable stack. Therefore the following patch
>> adds
On Sat, 2023-12-02 at 16:14 +0800, Lulu Cheng wrote:
/* snip */
> diff --git a/gcc/config/loongarch/loongarch-opts.cc
> b/gcc/config/loongarch/loongarch-opts.cc
> index b5836f198c0..6861642a98d 100644
> --- a/gcc/config/loongarch/loongarch-opts.cc
> +++ b/gcc/config/loongarch/loongarch-opts.cc
>
Hi,
> this patch extends the previous version by adding further code testing
> the presence of an optional deferred-length character argument also
> in the function initialization code. This allows to re-enable a
> commented-out test in v2.
Nice, that sounds logical.
> Regtested on
> Bootstrapped/regtested on x86_64-pc-linux-gnu, ok for trunk?
>
> -- >8 --
> It came up that a good hardening strategy is to disable trampolines
> which may require executable stack. Therefore the following patch
> adds -Werror=trampolines to -fhardened.
This would add a warning about
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112816
Jakub Jelinek changed:
What|Removed |Added
Keywords|needs-bisection |
--- Comment #5 from Jakub Jelinek
> Thanks. I can't push it myself - could you do that for me?
Pushed.
FX
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112816
--- Comment #4 from Jakub Jelinek ---
I think we want to add some patterns for combine which would match
(set (reg:V4SI 115)
(eq:V4SI (lshiftrt:V4SI (subreg:V4SI (reg:V2DI 110) 0)
(const_int 31 [0x1f]))
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112816
Jakub Jelinek changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
> mcmodel=large s not supported (yet) on any Darwin arch [PR90698], so the test
> needs skipping or xfailing, I think (either way with a reference to the PR).
Pushed as
https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=b74981b5cf32ebf4bfffd25e7174b5c80243447a
FX
Pushed to r14-6072.
在 2023/11/28 下午3:38, Li Wei 写道:
In LoongArch, the vector popcount has corresponding instructions, while
the scalar does not. Currently, the scalar popcount is calculated
through a loop, and the value of a non-power of two needs to be iterated
several times, so the vector
在 2023/11/29 下午5:44, Xi Ruoyao 写道:
On Tue, 2023-11-28 at 15:39 +0800, Li Wei wrote:
For vector constant extract-{even/odd} permutation replace the default
[x]vshuf instruction combination with [x]vilv{l/h} instruction, which
can reduce instructions and improves performance.
gcc/ChangeLog:
Pushed to r14-6070.
在 2023/11/29 上午9:53, Xi Ruoyao 写道:
On Tue, 2023-11-28 at 15:56 +0800, Li Wei wrote:
In the r14-5547 commit, C[LT]Z_DEFINED_VALUE_AT_ZERO were defined at
the same time, but in fact, CLZ_DEFINED_VALUE_AT_ZERO has already been
defined, so remove the duplicate definition.
From: Xi Ruoyao
We'll use HOST_WIDE_INT in LoongArch static properties in following patches.
Switch loongarch-def from C to C++ to make it possible.
To keep the same readability as C99 designated initializers, create a
std::array like data structure with position setter function, and add
field
1. Rebase Xi Ruoyao's patch to the latest commit.
https://gcc.gnu.org/pipermail/gcc-patches/2023-November/636798.html
2. Described in LoongArch Reference Manual v1.1:
The new functional subsets in each new version have independent identification
bits in the return value of the CPUCFG instruction.
The instructions defined in LoongArch Reference Manual v1.1 are not the
instruction
set v1.1 version. The CPU defined later may only support some instructions in
LoongArch Reference Manual v1.1. Therefore, the macro ISA_BASE_LA64V110 and
related definitions are removed here.
gcc/ChangeLog:
95 matches
Mail list logo