From: chenglulu
* contrib/config-list.mk: Add LoongArch triplet.
* gcc/doc/install.texi: Add LoongArch options section.
* gcc/doc/invoke.texi: Add LoongArch options section.
* gcc/doc/md.texi: Add LoongArch options section.
---
contrib/config-list.mk | 5 +-
From: chenglulu
* config/picflag.m4: Default add build option '-fpic' for LoongArch.
* configure: Add LoongArch tuples.
* configure.ac: Like wise.
---
config/picflag.m4 | 3 +++
configure | 10 +-
configure.ac | 10 +-
3 files changed, 21
From: chenglulu
gcc/testsuite/
* g++.dg/cpp0x/constexpr-rom.C: Add build options for LoongArch.
* g++.old-deja/g++.abi/ptrmem.C: Add LoongArch support.
* g++.old-deja/g++.pt/ptrmem6.C: xfail for LoongArch.
* gcc.dg/20020312-2.c: Add LoongArch support.
*
From: chenglulu
libgomp/
* configure.tgt: Add LoongArch triplet.
---
libgomp/configure.tgt | 4
1 file changed, 4 insertions(+)
diff --git a/libgomp/configure.tgt b/libgomp/configure.tgt
index d4f1e741b5a..2cd7272fcd8 100644
--- a/libgomp/configure.tgt
+++ b/libgomp/configure.tgt
From: chenglulu
libgcc/
* config/loongarch/crtfastmath.c: New file.
* config/loongarch/crti.S: Like wise.
* config/loongarch/crtn.S: Like wise.
* config/loongarch/lib2funcs.c: Like wise.
* config/loongarch/linux-unwind.h: Like wise.
*
From: chenglulu
---
libgcc/configure | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libgcc/configure b/libgcc/configure
index 4919a56f518..150ea04cb3d 100755
--- a/libgcc/configure
+++ b/libgcc/configure
@@ -5066,7 +5066,7 @@ $as_echo "$libgcc_cv_cfi" >&6; }
# word size
From: chenglulu
gcc/
* config/loongarch/larchintrin.h: New file.
* config/loongarch/loongarch-builtins.c: New file.
---
gcc/config/loongarch/larchintrin.h| 413 +
gcc/config/loongarch/loongarch-builtins.c | 511 ++
2 files changed,
From: chenglulu
gcc/
*config/loongarch/loongarch-c.c
---
gcc/config/loongarch/loongarch-c.c | 136 +
1 file changed, 136 insertions(+)
create mode 100644 gcc/config/loongarch/loongarch-c.c
diff --git a/gcc/config/loongarch/loongarch-c.c
From: chenglulu
gcc/
* common/config/loongarch/loongarch-common.c: New file.
* config/loongarch/genopts/genstr.sh: New file.
* config/loongarch/genopts/loongarch-strings: New file.
* config/loongarch/genopts/loongarch.opt.in: New file.
*
From: chenglulu
---
gcc/configure | 63 ++-
1 file changed, 57 insertions(+), 6 deletions(-)
diff --git a/gcc/configure b/gcc/configure
index a5160da83ec..2c95ceec398 100755
--- a/gcc/configure
+++ b/gcc/configure
@@ -7865,6 +7865,9 @@ else
The LoongArch architecture (LoongArch) is an Instruction Set
Architecture (ISA) that has a Reduced Instruction Set Computer (RISC)
style.
The documents are on
https://loongson.github.io/LoongArch-Documentation/README-EN.html
The ELF ABI Documents are on:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64961
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67012
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |9.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51501
Andrew Pinski changed:
What|Removed |Added
Status|SUSPENDED |NEW
Known to fail|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60625
Andrew Pinski changed:
What|Removed |Added
Last reconfirmed||2021-12-10
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48518
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |INVALID
See Also|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=42355
Andrew Pinski changed:
What|Removed |Added
Last reconfirmed|2010-01-04 19:39:44 |2021-12-9
Known to fail|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=31164
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99932
--- Comment #7 from Tom de Vries ---
(In reply to Tom de Vries from comment #6)
> (In reply to Tom de Vries from comment #5)
> > FIled https://developer.nvidia.com/nvidia_bug/3299227
>
> Nvidia reported it will be fixed in the next major cuda
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87656
--- Comment #10 from Eric Gallager ---
(In reply to Segher Boessenkool from comment #9)
> (In reply to Eric Gallager from comment #8)
> > Any reason not to put -Wnested-externs in -Wall or -Wextra?
>
> It warns for any "extern" declaration in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103529
Iain Buclaw changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
Jiufu Guo writes:
> Richard Biener writes:
>
>> On Mon, 18 Oct 2021, Jiufu Guo wrote:
>>
>>> With reference the discussions in:
>>> https://gcc.gnu.org/pipermail/gcc-patches/2021-July/574334.html
>>> https://gcc.gnu.org/pipermail/gcc-patches/2021-June/572006.html
>>>
Hi,
This patch updates the gdc codegen interface for the new front-end.
Bootstrapped and regression tested on x86_64-linux-gnu, committed to
mainline.
Regards,
Iain.
---
gcc/d/ChangeLog:
* Make-lang.in (D_FRONTEND_OBJS): Add d/root-optional.o.
* d-attribs.cc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103529
--- Comment #3 from CVS Commits ---
The master branch has been updated by Iain Buclaw :
https://gcc.gnu.org/g:9c7d5e8846edb28e5421211ee8eaad93e234de2c
commit r12-5887-g9c7d5e8846edb28e5421211ee8eaad93e234de2c
Author: Iain Buclaw
Date: Fri
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103528
--- Comment #4 from CVS Commits ---
The master branch has been updated by Iain Buclaw :
https://gcc.gnu.org/g:9c7d5e8846edb28e5421211ee8eaad93e234de2c
commit r12-5887-g9c7d5e8846edb28e5421211ee8eaad93e234de2c
Author: Iain Buclaw
Date: Fri
On Linux/x86_64,
f8463b0e3ec2438b4cfb8c9a468d59761db2c8a0 is the first bad commit
commit f8463b0e3ec2438b4cfb8c9a468d59761db2c8a0
Author: Jonathan Wakely
Date: Thu Dec 2 13:19:41 2021 +
libstdc++: Disable over-zealous warnings about std::string copies [PR103332]
caused
FAIL:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100786
Andrew Pinski changed:
What|Removed |Added
Keywords||ice-on-invalid-code
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103623
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |12.0
Summary|error: unable
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103510
--- Comment #5 from ashimida ---
(In reply to Andrew Pinski from comment #3)
> The only registers which are saved are the callee saved register IIRC. So
> you need to know the ABI.
Hi Andrew,
Is it reasonable to save all registers (include
Tested uild-x86_64-pc-linux-gnu, pushed to trunk and gcc-11.
On Thu, Nov 25, 2021 at 1:24 PM Jonathan Wakely wrote:
> On Wed, 24 Nov 2021 at 01:27, Thomas Rodgers wrote:
> >
> > const qualification was also missing in the free functions for
> wait/wait_explicit/notify_one/notify_all. Revised
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102994
--- Comment #2 from CVS Commits ---
The releases/gcc-11 branch has been updated by Thomas Rodgers
:
https://gcc.gnu.org/g:aca7d4e8790bff32ee749936bb0224d873c46052
commit r11-9371-gaca7d4e8790bff32ee749936bb0224d873c46052
Author: Thomas
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102994
--- Comment #1 from CVS Commits ---
The master branch has been updated by Thomas Rodgers :
https://gcc.gnu.org/g:38c60e5075f89265a560eab166d43247624a7535
commit r12-5886-g38c60e5075f89265a560eab166d43247624a7535
Author: Thomas Rodgers
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103640
--- Comment #3 from Andrew Pinski ---
(In reply to Nick Desaulniers from comment #0)
> While we can change this in clang (https://reviews.llvm.org/D115471), I do
> think it would be more ergonomic for developers if the order of operands for
>
On 12/9/21 5:38 PM, Martin Sebor wrote:
On 12/9/21 4:24 PM, Jonathan Wakely via Gcc-patches wrote:
These warnings are triggered by perfectly valid code using std::string.
They're particularly bad when --enable-fully-dynamic-string is used,
because even std::string().begin() will give a warning.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103623
Kewen Lin changed:
What|Removed |Added
CC||linkw at gcc dot gnu.org
--- Comment #1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103640
--- Comment #2 from Andrew Pinski ---
Since the feature of out inline-asm with gotos was added in GCC 11, the manual
has always been clear for released versions of GCC with the support for it.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98096
Andrew Pinski changed:
What|Removed |Added
CC||ndesaulniers at google dot com
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103640
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |DUPLICATE
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103639
Eric Gallager changed:
What|Removed |Added
CC||egallager at gcc dot gnu.org,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103640
Bug ID: 103640
Summary: asm goto w/ outputs numbering with tied outputs
differs from clang
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
On Wed, Dec 8, 2021 at 6:10 PM Jeff Law via Gcc-patches
wrote:
>
>
>
> On 12/7/2021 2:55 AM, Jakub Jelinek wrote:
> > Hi!
> >
> > The following patch adds support for relocation of the PCH blob on PCH
> > restore if we don't manage to get the preferred map slot for it.
> > The GTY stuff knows
Hi,
This patch aligns all D defined methods to MINIMUM_METHOD_BOUNDARY,
improving interoperability with C++ methods.
Bootstrapped and regression tested on x86_64-linux-gnu, committed to
mainline and backported to the release branches.
Regards,
Iain.
gcc/d/ChangeLog:
* decl.cc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56670
Vivek Rao changed:
What|Removed |Added
CC||vivekrao4 at yahoo dot com
--- Comment #13
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67491
Bug 67491 depends on bug 71174, which changed state.
Bug 71174 Summary: [concepts] Segmentation fault while processing concepts error
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71174
What|Removed |Added
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71174
Andrew Pinski changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103635
Andrew Pinski changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71982
--- Comment #3 from Andrew Pinski ---
Trunk gives:
[apinski@xeond2 src]$ ~/upstream-gcc/bin/gcc t.cc
t.cc: In instantiation of ‘bool operator==(const A&, const A&) [with T =
const B]’:
t.cc:25:30: required from here
t.cc:1:34: error: no match
On 12/9/21 4:24 PM, Jonathan Wakely via Gcc-patches wrote:
These warnings are triggered by perfectly valid code using std::string.
They're particularly bad when --enable-fully-dynamic-string is used,
because even std::string().begin() will give a warning.
Use pragmas to stop the troublesome
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103635
--- Comment #4 from Mark Harmstone ---
Thanks, but I mentioned just to illustrate that this isn't purely a
hypothetical bug.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103635
--- Comment #3 from Jonathan Wakely ---
There's an explicit instantiation declaration at the end of the header, which
means the entire thing is externally defined in libstdc++.so and the only code
that gets instantiated in your own translation
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103637
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |12.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103636
Andrew Pinski changed:
What|Removed |Added
Keywords||ice-on-valid-code
Target
On 12/9/21 3:58 PM, Jim Wilson wrote:
On Mon, Nov 29, 2021 at 5:21 PM Martin Sebor via Gcc-patches
mailto:gcc-patches@gcc.gnu.org>> wrote:
There are some other "unusual" cases worth a look, such as missing
context of any kind except for like and column:
elfnn-riscv.c:3346:7:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103638
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |11.3
On Thu, Dec 09, 2021 at 09:42:04AM -0700, Martin Sebor wrote:
> On 12/6/21 12:40 PM, Segher Boessenkool wrote:
> >Named address spaces are completely target-specific.
>
> My understanding of these kernel/user address spaces that David
> is adding for the benefit of the analyzer is that the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103382
--- Comment #6 from Jonathan Wakely ---
The incorrect noexcept is fixed for GCC 12, but isn't suitable to backport.
For the branches we should consider disabling cancellation as suggested in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85813
Jonathan Wakely changed:
What|Removed |Added
Status|NEW |RESOLVED
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59769
Jonathan Wakely changed:
What|Removed |Added
Target Milestone|--- |12.0
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92300
Jonathan Wakely changed:
What|Removed |Added
Status|NEW |RESOLVED
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103630
Jonathan Wakely changed:
What|Removed |Added
Summary|[9/10/11/12 Regression] |[9/10/11 Regression]
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64135
Jonathan Wakely changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
Tested powerpc64le-linux, pushed to trunk.
Since r11-1571 (c++: Refinements to "more constrained") was changed in
the front end, the following comment from stl_iterator.h stopped being
true:
// These extra overloads are not needed in C++20, because the ones above
// are constrained with a
Tested powerpc64le-linux, pushed to trunk.
This test no longer has additional errors for C++20 mode, so remove the
dg-error that is now failing, and the unnecessary dg-prune-output.
libstdc++-v3/ChangeLog:
* testsuite/20_util/scoped_allocator/69293_neg.cc: Remove
dg-error for
Tested powerpc64le-linux, pushed to trunk.
This allows std::make_exception_ptr to be used in a translation unit
compiled with -fno-exceptions. This works because the new implementation
added for PR 68297 doesn't need to throw or catch anything. The catch is
there to handle exceptions from the
Tested powerpc64le-linux, pushed to trunk.
This restores support for std::make_exception_ptr and for using
std::exception_ptr in C++98.
Because the new non-throwing implementation needs to use std::decay to
handle references the original throwing implementation is used for
C++98.
We also need
Tested powerpc64le-linux, pushed to trunk.
This implements my P2467R0 proposal to support opening an fstream in
exclusive mode. The new constant is also supported pre-C++23 as
std::ios_base::__noreplace.
This proposal hasn't been approved for C++23 yet, but I am confident it
will be, as this is
On Wed, 8 Dec 2021 at 17:26, Jonathan Wakely wrote:
>
> On Wed, 8 Dec 2021 at 00:36, Jonathan Wakely wrote:
> >
> > On Tue, 7 Dec 2021 at 21:52, Florian Weimer wrote:
> > >
> > > * Jonathan Wakely:
> > >
> > > > On Tue, 7 Dec 2021, 21:20 Florian Weimer via Libstdc++,
> > > >
> > > > wrote:
> > >
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68297
--- Comment #5 from CVS Commits ---
The master branch has been updated by Jonathan Wakely :
https://gcc.gnu.org/g:a8e02a00a0fcac42657c8ef7921566e42db8ef49
commit r12-5880-ga8e02a00a0fcac42657c8ef7921566e42db8ef49
Author: Jonathan Wakely
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85813
--- Comment #10 from CVS Commits ---
The master branch has been updated by Jonathan Wakely :
https://gcc.gnu.org/g:a8e02a00a0fcac42657c8ef7921566e42db8ef49
commit r12-5880-ga8e02a00a0fcac42657c8ef7921566e42db8ef49
Author: Jonathan Wakely
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103630
--- Comment #2 from CVS Commits ---
The master branch has been updated by Jonathan Wakely :
https://gcc.gnu.org/g:a1ca039fc0fe934ef36c25d8284e6e116bcaffa7
commit r12-5879-ga1ca039fc0fe934ef36c25d8284e6e116bcaffa7
Author: Jonathan Wakely
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59769
--- Comment #5 from CVS Commits ---
The master branch has been updated by Jonathan Wakely :
https://gcc.gnu.org/g:a219139e986a4200a9105d7c1fa63735d2945994
commit r12-5878-ga219139e986a4200a9105d7c1fa63735d2945994
Author: Jonathan Wakely
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103382
--- Comment #5 from CVS Commits ---
The master branch has been updated by Jonathan Wakely :
https://gcc.gnu.org/g:9e18a25331fa25c3907249fede65a02c6817b06e
commit r12-5877-g9e18a25331fa25c3907249fede65a02c6817b06e
Author: Jonathan Wakely
Tested powerpc64le-linux, pushed to trunk.
Inserting a pair into a map will allocate a new
node and construct a pair in the node, then check if
the Key is already present in the map. That is because pair
is not the same type as the map's value_type. But it only differs in the
const-qualification
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92300
--- Comment #6 from CVS Commits ---
The master branch has been updated by Jonathan Wakely :
https://gcc.gnu.org/g:db5fa0837e464b595a3d63766060bae1c9ac5ccc
commit r12-5876-gdb5fa0837e464b595a3d63766060bae1c9ac5ccc
Author: Jonathan Wakely
Date:
On Thu, 2 Dec 2021 at 17:21, Jonathan Wakely via Libstdc++
wrote:
>
> Apart from "don't bother changing the COW string", does anybody see a
> reason we shouldn't do this? This passes all tests for normal COW
> strings and fully-dynamic COW strings.
Pushed to trunk.
>
> When non-const
On Thu, 2 Dec 2021 at 17:22, Jonathan Wakely via Libstdc++
wrote:
>
> I'd like to push this to trunk to fix PR64135.
The attached patch is what I've pushed to trunk, which adds some doc updates.
> It think this fixes the use of a non-reserved name, while preserving the
> ABI as far as class
These warnings are triggered by perfectly valid code using std::string.
They're particularly bad when --enable-fully-dynamic-string is used,
because even std::string().begin() will give a warning.
Use pragmas to stop the troublesome warnings for copies done by
std::char_traits.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103483
--- Comment #11 from CVS Commits ---
The master branch has been updated by Jonathan Wakely :
https://gcc.gnu.org/g:f8463b0e3ec2438b4cfb8c9a468d59761db2c8a0
commit r12-5874-gf8463b0e3ec2438b4cfb8c9a468d59761db2c8a0
Author: Jonathan Wakely
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103332
--- Comment #6 from CVS Commits ---
The master branch has been updated by Jonathan Wakely :
https://gcc.gnu.org/g:f8463b0e3ec2438b4cfb8c9a468d59761db2c8a0
commit r12-5874-gf8463b0e3ec2438b4cfb8c9a468d59761db2c8a0
Author: Jonathan Wakely
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102958
--- Comment #4 from CVS Commits ---
The master branch has been updated by Jonathan Wakely :
https://gcc.gnu.org/g:f8463b0e3ec2438b4cfb8c9a468d59761db2c8a0
commit r12-5874-gf8463b0e3ec2438b4cfb8c9a468d59761db2c8a0
Author: Jonathan Wakely
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64135
--- Comment #3 from CVS Commits ---
The master branch has been updated by Jonathan Wakely :
https://gcc.gnu.org/g:fe9571a35db53e5203326f854f73e432691d67f6
commit r12-5873-gfe9571a35db53e5203326f854f73e432691d67f6
Author: Jonathan Wakely
Date:
On 12/9/21 15:15, Jakub Jelinek wrote:
On Wed, Dec 08, 2021 at 08:53:03AM -0500, Jason Merrill wrote:
As mentioned in the PR, the varpool/middle-end code is trying to be
conservative with address comparisons of different vars if those vars
don't bind locally, because of possible aliases in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103635
--- Comment #2 from Mark Harmstone ---
(In reply to Jonathan Wakely from comment #1)
> (In reply to Mark Harmstone from comment #0)
> > The practical problem this causes is that you can't #include on
> > mingw with -mabi=sysv,
>
> I don't
On Mon, Nov 29, 2021 at 5:21 PM Martin Sebor via Gcc-patches <
gcc-patches@gcc.gnu.org> wrote:
> There are some other "unusual" cases worth a look, such as missing
> context of any kind except for like and column:
>
> elfnn-riscv.c:3346:7: warning: statement after return is not reachable
>
On 11/13/21 1:37 PM, David Malcolm via Gcc-patches wrote:
This patch adds a new:
__attribute__((untrusted))
for use by the C front-end, intended for use by the Linux kernel for
use with "__user", but which could be used by other operating system
kernels, and potentialy by other projects.
Snapshot gcc-9-20211209 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/9-20211209/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 9 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103635
--- Comment #1 from Jonathan Wakely ---
(In reply to Mark Harmstone from comment #0)
> The practical problem this causes is that you can't #include on
> mingw with -mabi=sysv,
I don't think that's going to work anyway, is it?
I would expect
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103609
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Resolution|--- |FIXED
The conversion of a MEM address to ptr_mode in
try_store_by_multiple_pieces was misguided: copy_addr_to_reg expects
Pmode for addresses.
Regstrapped on x86_64-linux-gnu, testcase verified with a cross to
aarch64. Ok to install?
for gcc/ChangeLog
PR target/100518
*
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103609
--- Comment #5 from CVS Commits ---
The releases/gcc-11 branch has been updated by Harald Anlauf
:
https://gcc.gnu.org/g:81ffb19017daf7197445ed0793e925674a3970d5
commit r11-9368-g81ffb19017daf7197445ed0793e925674a3970d5
Author: Harald Anlauf
The testcase confuses the code that detects min and max len for the
memset, so max_len ends up less than min_len. That shouldn't be
possible, but the testcase requires us to handle this case.
The store-by-mult-pieces algorithm actually relies on min and max
lengths, so if we find them to be
Excerpts from Andreas Schwab's message of December 9, 2021 11:09 am:
> Breaks aarch64:
>
> ../../../../libphobos/libdruntime/core/sys/linux/unistd.d:10:15: error:
> module 'core.sys.linux.syscalls' import 'SystemCall' not found
>10 | public import core.sys.linux.syscalls : SystemCall;
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=21678
Jason Merrill changed:
What|Removed |Added
CC||jason at gcc dot gnu.org
--- Comment
Hi Mikael,
Am 08.12.21 um 10:32 schrieb Mikael Morin:
On 07/12/2021 21:46, Harald Anlauf wrote:
Hi Mikael,
Am 07.12.21 um 21:17 schrieb Mikael Morin:
The existing code looks dubious to me (or at least difficult to
understand), and your patch doesn’t make that any better.
I would rather try
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103639
js-gcc at webkeks dot org changed:
What|Removed |Added
Keywords|wrong-code |
--- Comment #4 from js-gcc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103639
Andrew Pinski changed:
What|Removed |Added
Ever confirmed|0 |1
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103622
--- Comment #5 from Bill Schmidt ---
Expected behavior is:
pr103622.c: In function 'get_float128_exponent':
pr103622.c:4:3: error: invalid parameter combination for AltiVec intrinsic
'__builtin_vec_scalar_extract_exp'
4 | return
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98782
--- Comment #21 from pthaugen at gcc dot gnu.org ---
(In reply to Jan Hubicka from comment #20)
> With g:r12-5872-gf157c5362b4844f7676cae2aba81a4cf75bd68d5 we should no
> longer need -fno-inline-functions-called-once
Yes, I see that now with an
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103622
Bill Schmidt changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |wschmidt at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103639
--- Comment #2 from js-gcc at webkeks dot org ---
Oh, forgot to clarify in the example:
Assume more than 1 object in the collection and someVar to be 0.
1 - 100 of 279 matches
Mail list logo
