Hi all,
This patch aims to fix the cvtps2pd insn, which should also work on
memory operand but currently does not. After this fix, when loop == 2,
it will eliminate movq instruction.
Regtested on x86_64-pc-linux-gnu. Ok for trunk?
BRs,
Haochen
gcc/ChangeLog:
PR target/43618
*
> Am 29.06.2022 um 22:44 schrieb Joseph Myers :
>
> The LTO merging of options from different input files was broken by:
>
> commit 227a2ecf663d69972b851f51f1934d18927b62cd
> Author: Martin Liska
> Date: Fri Mar 12 11:53:47 2021 +0100
>
>lto-wrapper: Use vec data type.
>
>
> Am 30.06.2022 um 03:43 schrieb Andrew MacLeod via Gcc-patches
> :
>
> The routine which tried to fold and's and or's using relations was using the
> dependency cache as a shortcut to determine if there were 2 ssa names on the
> feeding expressions, and assuming that was correct.
>
> ie
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105614
--- Comment #13 from Chris Packham ---
(In reply to Xi Ruoyao from comment #12)
> Please provide info about how libsanitizer end up building with GCC 11.3 and
> MIPS64 (such a combination is not supported and libsanitizer should not be
>
In libsanitizer code, the size of some GNU libc data structure (notably,
struct stat) is hard coded. These sizes may trigger a static assert
buidling against another libc.
Just make non-GNU libc targets UNSUPPORTED now. If someone really cares
about those alternative libc implementations,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106136
Xi Ruoyao changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Assignee|unassigned at
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105614
Xi Ruoyao changed:
What|Removed |Added
Status|NEW |WAITING
--- Comment #12 from Xi Ruoyao
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106141
--- Comment #2 from Jason Liam ---
Note that if `child.hh` is included in multiple TUs, then the program will have
UB NDR as in each TU as the template argument in `Base` is a pointer to
an entity with internal linkage meaning in each TU it
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86491
--- Comment #11 from Andrew Pinski ---
(In reply to Jonathan Wakely from comment #8)
> A variable declared 'static' has internal linkage, and so does a variable in
> an anonymous namespace, which is probably the source of the mix-up in GCC's
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106141
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |DUPLICATE
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86491
Andrew Pinski changed:
What|Removed |Added
CC||jlame646 at gmail dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106141
Bug ID: 106141
Summary: Better wording for warning: ‘Child’ has a base
‘Base<(& hello)>’ whose type uses the anonymous
namespace [-Wsubobject-linkage]
Product: gcc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106136
Xi Ruoyao changed:
What|Removed |Added
Status|RESOLVED|UNCONFIRMED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105614
--- Comment #11 from Xi Ruoyao ---
> Removing my "fix" resolves the issue for GCC 12 but I suspect something like
> the suggestion from https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105614#c7
> might resolve the issue properly.
I don't think
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106022
--- Comment #17 from Hongtao.liu ---
(In reply to H.J. Lu from comment #16)
> Created attachment 53227 [details]
> The v4 patch
>
> Here is a different approach by supporting 2/4/8 byte constant vector stores.
It LGTM.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106126
--- Comment #13 from luoxhu at gcc dot gnu.org ---
Otherwise we need record first_bb when conditions_in_bbs->is_empty, then check
that in is_beneficial, ordered_remove the info entry if that bb is not the
first "if condition" with side_effect
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105614
Xi Ruoyao changed:
What|Removed |Added
CC||xry111 at gcc dot gnu.org
--- Comment #10
Hi,
We've made a consensus [1] that not to enable trapping for division by
zero by default for LLVM, and we think GCC should behave similarly.
The main rationales:
1. Division by zero is undefined behavior, so in theory any portable
program shall not depend on it.
2. There are already many
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106126
--- Comment #12 from luoxhu at gcc dot gnu.org ---
conditions_in_bbs->is_empty doesn't mean that range is at the start of switch
condition:(, so couldn't assume to ignore the no_side_effect_bb check?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106113
--- Comment #3 from kong lingling ---
(In reply to Jakub Jelinek from comment #1)
> Has the definition of these intrinsics changed over time?
Yes, intrinsic `_mm_comieq_ss ` old operation is `RETURN ( a[31:0] == b[31:0]
) ? 1 : 0`, and new
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106126
--- Comment #11 from luoxhu at gcc dot gnu.org ---
Sorry for breaking, my bugzilla account is luo...@gcc.gnu.org.
The patch seems reasonable to fold 65-90 ('A'-'Z') to switch statement,
4,6c4,6
< ;; Canonical GIMPLE case clusters: 33 60 62
Committed to trunk, thanks :)
Is it OK for gcc-11 and gcc-12 branches?
On Wed, Jun 29, 2022 at 5:00 PM Richard Biener wrote:
>
> On Tue, 28 Jun 2022, Kito Cheng wrote:
>
> > That warning won't happen on ilp32 targets, seems like Andrew Pinski
> > already mention that[1] before.
> >
> > Verified
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106113
H.J. Lu changed:
What|Removed |Added
Last reconfirmed||2022-06-30
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102690
--- Comment #14 from CVS Commits ---
The master branch has been updated by Kito Cheng :
https://gcc.gnu.org/g:0f6eef398045deb2a62d18b526831719c7c20c8a
commit r13-1357-g0f6eef398045deb2a62d18b526831719c7c20c8a
Author: Kito Cheng
Date: Tue
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63426
Bug 63426 depends on bug 106097, which changed state.
Bug 106097 Summary: undefined behaviors regarding integer shifts in
loongarch_build_integer
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106097
What|Removed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106097
Xi Ruoyao changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
> -Original Message-
> From: Jiang, Haochen
> Sent: Thursday, June 30, 2022 9:51 AM
> To: gcc-patches@gcc.gnu.org
> Cc: ubiz...@gmail.com; Liu, Hongtao
> Subject: [PATCH] i386: Add AVX512BW to AVX512F in MASK_ISA2
>
> Hi all,
>
> I just found in MASK_ISA2_UNSET part, since AVX512BW
Hi all,
I just found in MASK_ISA2_UNSET part, since AVX512BW is based on AVX512F, we
should add OPTION_MASK_ISA2_AVX512BW_UNSET to AVX512F for maintainence
convenience and logic correctness, or we will need to add all future ISAs based
on AVX512BW in both AVX512F and AVX512BW. This will be easily
The routine which tried to fold and's and or's using relations was using
the dependency cache as a shortcut to determine if there were 2 ssa
names on the feeding expressions, and assuming that was correct.
ie
_16 = a.0_1 < -117;
_17 = a.0_1 >= -83;
_18 = _16 | _17;
the dependency cache
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106114
--- Comment #9 from CVS Commits ---
The master branch has been updated by Andrew Macleod :
https://gcc.gnu.org/g:918bb0e78ae42bfcf808a1e93a8f6b9d02ea
commit r13-1356-g918bb0e78ae42bfcf808a1e93a8f6b9d02ea
Author: Andrew MacLeod
Date:
C++2017 and previous standard description:
The value of E1 << E2 is E1 left-shifted E2 bit positions;
vacated bits are zero-filled. If E1 has an unsigned type,
the value of the result is E1×2E2, reduced modulo one more
than the maximum value representable inthe result type.
Otherwise, if E1 has a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106131
--- Comment #6 from Xue Zhenliang <18307130172 at fudan dot edu.cn> ---
I'm trying to reducing it further. Now I've eliminated the dependency on STL:
struct Pair {
int a, b;
Pair(const Pair &) = default;
Pair(int _a, int _b) :
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106095
Antoni changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106095
--- Comment #2 from CVS Commits ---
The master branch has been updated by Antoni Boucher :
https://gcc.gnu.org/g:e484755aecd543b4c9e2adb4f348118c1e43cfd0
commit r13-1355-ge484755aecd543b4c9e2adb4f348118c1e43cfd0
Author: Antoni Boucher
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105812
Antoni changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105812
--- Comment #2 from CVS Commits ---
The master branch has been updated by Antoni Boucher :
https://gcc.gnu.org/g:e3a5c77388ae3791afed4f4286ec7e41e5b9f7c3
commit r13-1353-ge3a5c77388ae3791afed4f4286ec7e41e5b9f7c3
Author: Antoni Boucher
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100157
--- Comment #1 from Jonathan Wakely ---
GCC doesn't support template-like built-ins, but I have a patch to add a
function-like __builtin_type_pack_element(N, T...) instead. I don't like the
name "type pack element" much though. To me that
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100157
Jonathan Wakely changed:
What|Removed |Added
Target Milestone|--- |13.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100157
Jonathan Wakely changed:
What|Removed |Added
Last reconfirmed||2022-06-29
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104477
--- Comment #3 from Andrew Pinski ---
I am going to be like Johnathan and say I wish these compiler intrinsic were
defined by the standard rather than having to define them ourselves.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104477
Marek Polacek changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
On Tue, Jun 28, 2022 at 7:32 AM Sören Tempel wrote:
>
> Ian Lance Taylor wrote:
> > Given that pretty much every one of these musl patches has led to
> > problems on some glibc systems, it would be very nice if you could do
> > some testing with glibc. Thanks.
>
> Sorry, my bad.
>
> I just
This patch to the Go frontend checks repeated const expressions in new
scope, in case they refer to a newly defined name. The test case is
const8.go in https://go.dev/cl/414795. This fixes
https://go.dev/issue/53585. Bootstrapped and ran Go testsuite on
x86_64-pc-linux-gnu. Committed to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106140
Bug ID: 106140
Summary: RFE: analyzer could complain about misuses of socket
APIs
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106022
H.J. Lu changed:
What|Removed |Added
Attachment #53186|0 |1
is obsolete|
Hello
The devel/omp/gcc-12 branch has been pushed to the git repo as the
development branch for new OpenMP, OpenACC and offloading functionality,
based on the GCC 12 branch.
The git doc page has been modified to point to the new branch as the
active OMP development branch, while the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106117
--- Comment #8 from John McCall ---
Oh, that's what I get for having two different draft standards open at once.
Thanks.
On 6/28/22 13:01, Qing Zhao wrote:
On Jun 28, 2022, at 2:49 PM, Jakub Jelinek wrote:
On Tue, Jun 28, 2022 at 06:29:01PM +, Qing Zhao wrote:
On Jun 28, 2022, at 2:22 PM, Jakub Jelinek wrote:
On Tue, Jun 28, 2022 at 06:15:58PM +, Qing Zhao wrote:
Because the flag just tells
Hi,
Casting from vector to static array is permitted in the D, and the
front-end generates a reinterpret cast, but casting back the other way
resulted in an error.
This has been fixed to be properly handled in the code generation pass
of VectorExp, and the conversion for lvalue and rvalue
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106139
--- Comment #2 from CVS Commits ---
The master branch has been updated by Iain Buclaw :
https://gcc.gnu.org/g:329bef49da30158d30fed1106002bb71674776bd
commit r13-1351-g329bef49da30158d30fed1106002bb71674776bd
Author: Iain Buclaw
Date: Wed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106139
--- Comment #1 from Iain Buclaw ---
Note, gdc-11 and gdc-10 error as a result to a different issue.
---
cannot resolve type for cast(__vector(int[8]))arr
---
Fix was made in a newer version of upstream dmd, so that'll be handled in the
Hi, Jakub and Joseph:
> On Jun 28, 2022, at 12:43 PM, Jakub Jelinek wrote:
>
> On Tue, Jun 28, 2022 at 03:59:22PM +, Qing Zhao via Gcc-patches wrote:
>>> On Jun 28, 2022, at 11:08 AM, Jakub Jelinek wrote:
>>>
>>> On Tue, Jun 28, 2022 at 03:03:12PM +, Qing Zhao wrote:
2. Then
The LTO merging of options from different input files was broken by:
commit 227a2ecf663d69972b851f51f1934d18927b62cd
Author: Martin Liska
Date: Fri Mar 12 11:53:47 2021 +0100
lto-wrapper: Use vec data type.
Previously, find_and_merge_options would merge options it read into
those in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105243
--- Comment #11 from Steve Kargl ---
On Wed, Jun 29, 2022 at 07:42:30PM +, anlauf at gcc dot gnu.org wrote:
>
> when using your patch from comment#2 and moving it up slightly, it will
> also improve error handling for unlimited polymorphic
On Wed, Jun 29, 2022 at 08:10:10PM +0200, Tobias Burnus wrote:
> > > + if (output_requires)
> > > +{
> > > + HOST_WIDE_INT val = ((HOST_WIDE_INT) omp_requires_mask
> > > + & (OMP_REQUIRES_UNIFIED_ADDRESS
> > > + |
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106117
--- Comment #7 from joseph at codesourcery dot com ---
FLT_EVAL_METHOD of 0 gives _Float16 excess precision ("evaluate all
operations and constants, whose semantic type comprises a set of values
that is a strict subset of the values of float,
Currently, this is a rather useless patch - even though it helps to reduce
the number of local patches I have. Due to the printed sorry, adding a
testcase with -fdump-tree-* is also not possible, yet.
For reverse offload, the plan is to call
GOMP_target_ext
inside the on the device, passing
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105243
--- Comment #10 from anlauf at gcc dot gnu.org ---
Submitted: https://gcc.gnu.org/pipermail/fortran/2022-June/057972.html
Dear all,
a CLASS entity cannot have the PARAMETER attribute.
This is detected in some situations, but in others
we ICE because we never reach the existing check.
Adding a similar check when handling the declaration
improves error recovery.
The initial patch is by Steve. I adjusted and moved
it
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105243
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |anlauf at gcc dot
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106131
--- Comment #5 from Marek Polacek ---
Started with
commit 8403c2cf5f66758fc78a01a675b0d218fded0202
Author: Richard Biener
Date: Mon Nov 24 14:07:18 2014 +
re PR target/63679 ([AArch64] Failure to constant fold.)
2014-11-24
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106131
Marek Polacek changed:
What|Removed |Added
Last reconfirmed||2022-06-29
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106131
Marek Polacek changed:
What|Removed |Added
Keywords|needs-bisection |
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104637
Jakub Jelinek changed:
What|Removed |Added
Target Milestone|10.5|10.4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106131
Andrew Pinski changed:
What|Removed |Added
Target Milestone|12.2|10.5
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106131
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |12.2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104637
Uroš Bizjak changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106114
--- Comment #8 from Andrew Macleod ---
Created attachment 53226
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53226=edit
proposed patch
Patch in testing
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106102
--- Comment #7 from CVS Commits ---
The master branch has been updated by Sergei Trofimovich :
https://gcc.gnu.org/g:49d508065bdd36fb1a9b6aad9666b1edb5e06474
commit r13-1350-g49d508065bdd36fb1a9b6aad9666b1edb5e06474
Author: Sergei Trofimovich
Hi Jakub,
On 29.06.22 19:02, Jakub Jelinek wrote:
On Wed, Jun 29, 2022 at 04:33:02PM +0200, Tobias Burnus wrote:
+ if (flag_openmp
+ && lookup_attribute ("omp declare target",
+ DECL_ATTRIBUTES (current_function_decl)))
+omp_requires_mask
+ = (enum
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95372
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Resolution|--- |FIXED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103993
--- Comment #4 from Ed Catmur ---
And another example, provoked by throwing new (this only happens at -Og):
#include
struct D {
D();
static void* operator new (std::size_t s) {
if (void* p = ::malloc(s))
return p;
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104637
--- Comment #16 from tt_1 ---
May I kindly ask why this was retargeted to gcc-10.5.0? It seems to me that all
the patches were merged into gcc-10.4.0, is there more to come?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106114
--- Comment #7 from Andrew Macleod ---
The routine which tries to fold relations in && or || statements is getting
stale information.
GORI maintains a dependency cache which is mostly use by the temporal mechanism
to decide when statements are
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106117
--- Comment #6 from John McCall ---
Ah, I can see how the FLT_EVAL_METHOD schema gives us a unifying scheme, thank
you. Just to be clear, though, the actual value of FLT_EVAL_METHOD in that
mode should be 0, correct?
In r13-1045-gcb7fd1ea85feea I assumed that substitution into generic
DECL_TI_ARGS corresponds to an identity mapping of the given arguments,
and hence its safe to always elide such substitution. But this PR
demonstrates that such a substitution isn't always the identity mapping,
in particular
On Wed, 2022-06-29 at 17:39 +0200, Tim Lange wrote:
> Hi,
Thanks for the updated patch.
Overall, looks nearly ready; various nits inline below, throughout...
>
> I've addressed most of the points from the review.
> * The allocation size warning warns whenever region_model::get_capacity
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106117
--- Comment #5 from joseph at codesourcery dot com ---
The idea with "16" is to say that's the exact FLT_EVAL_METHOD value
(defined in C23 Annex H) whose semantics should be followed. It would
affect float/double promotion on i386 as well
On Wed, Jun 29, 2022 at 12:42:04PM -0400, Jason Merrill wrote:
> > The usual case is that people just use -fsanitize=undefined
> > and get both return and unreachable sanitization, for fall through
> > into end of functions returning non-void done through return sanitization.
> >
> > In the rare
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106121
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Resolution|--- |FIXED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106121
--- Comment #6 from CVS Commits ---
The master branch has been updated by Harald Anlauf :
https://gcc.gnu.org/g:b8f284d3673004dffae714b56ed663467c2a52a7
commit r13-1349-gb8f284d3673004dffae714b56ed663467c2a52a7
Author: Harald Anlauf
Date:
On Wed, Jun 29, 2022 at 04:33:02PM +0200, Tobias Burnus wrote:
> --- a/gcc/c/c-parser.cc
> +++ b/gcc/c/c-parser.cc
> @@ -2488,6 +2488,12 @@ c_parser_declaration_or_fndef (c_parser *parser, bool
> fndef_ok,
> break;
> }
>
> + if (flag_openmp
> + && lookup_attribute ("omp
On 6/23/22 13:03, Lewis Hyatt via Gcc-patches wrote:
Hello-
https://gcc.gnu.org/pipermail/gcc-patches/2022-May/595556.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53431#c49
Would a C++ maintainer have some time to take a look at this patch
please? I feel like the PR is still worth
On 6/27/22 11:44, Jakub Jelinek wrote:
On Wed, Jun 22, 2022 at 12:04:59AM -0400, Jason Merrill wrote:
On 6/20/22 16:16, Jason Merrill wrote:
On 6/20/22 07:05, Jakub Jelinek wrote:
On Fri, Jun 17, 2022 at 05:20:02PM -0400, Jason Merrill wrote:
Related to PR104642, the current situation where
The macro location tables should really mention they are about
locations. So rename them. Also, add a missing free of the remapping
table, and remove some now-unneeded macro checking.
nathan
--
Nathan SidwellFrom b0f25e1fdc6199725e69023a3dc49021f311ba66 Mon Sep 17 00:00:00 2001
From: Nathan
Hi,
The variables being used to get the result out of TYPE_VECTOR_SUBPARTS
were being flagged by -Werror=maybe-uninitialized. As they have already
been checked for being constant earlier, use `to_constant' instead.
This patch is based on feedback from Andreas. Given the error they got,
this
In C++03, -Wc++11-compat should warn about
int constexpr;
since 'constexpr' is a keyword in C++11. Jonathan reports that
we don't emit a similar warning for 'alignas' or 'alignof', and,
as I found out, 'thread_local'.
Similarly, we don't warn for most C++20 keywords. That happens
because
Excerpts from Andreas Schwab's message of Juni 29, 2022 12:09 pm:
> make[3]: Entering directory '/opt/gcc/gcc-20220629/Build/gcc'
> /opt/gcc/gcc-20220629/Build/./prev-gcc/xg++
> -B/opt/gcc/gcc-20220629/Build/./prev-gcc/ -B/usr/aarch64-suse-linux/bin/
> -nostdinc++
> -B/opt/g
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53431
Lewis Hyatt changed:
What|Removed |Added
CC||gcc at behdad dot org
--- Comment #50
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100125
Lewis Hyatt changed:
What|Removed |Added
CC||lhyatt at gcc dot gnu.org
On Nios II, PIC function calls use R_NIOS2_CALL* relocations, which
may refer to a GOT entry that initially points to a PLT entry to
resolve the function on first call and that is then changed by the
dynamic linker to point directly to the function to be called so
subsequent calls do not go
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106101
--- Comment #8 from Segher Boessenkool ---
There is structural RTL checking in rtl.h (see RTL_CHECK{1,2,C1,C2,C3} and the
various ELT and INT accessors). This would be easier to use here if we used
some STRICT_LOW_PART_P everywhere :-)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106117
--- Comment #4 from John McCall ---
Ah, thank you, we weren't aware of -fexcess-precision=16. If that's the
precedent, we can certainly follow it.
The idea around "16" was to make it clear that this just affects _Float16? If
the option were
Hi,
I've addressed most of the points from the review.
* The allocation size warning warns whenever region_model::get_capacity returns
something useful, i.e. also on statically-allocated regions.
* I added a new virtual function to the pending-diagnostic class, so that it
is possible to emit a
Last time aarch64 libmvec was discussed, the OpenMP
declare variant syntax support was not ready in gcc
and there were open questions around how simd isa
variants would be supported.
https://gcc.gnu.org/pipermail/gcc-patches/2019-October/532940.html
The vector function ABI for aarch64 allows the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106137
--- Comment #5 from CVS Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:c022c0de2a6c9110350cd50275be97d061a19530
commit r13-1344-gc022c0de2a6c9110350cd50275be97d061a19530
Author: Jakub Jelinek
Date:
On 28.06.22 22:36, Harald Anlauf via Gcc-patches wrote:
the simplification of EXTENDS_TYPE_OF() did not handle the
situation that one of its arguments were a CLASS variable
that was improperly declared. NULL pointer dereference.
The fix is obvious. Steve found a similar solution, which
is
On 29.06.22 14:15, Jakub Jelinek via Fortran wrote:
My patch apparently left some __float128 uses in libgfortran
that could use _Float128 instead, the following patch changes that.
Ok for trunk?
LGTM. Thanks!
Tobias
2022-06-29 Jakub Jelinek
* mk-kinds-h.sh: Change __float128 to
Hi all,
Here is the agenda for tomorrow's RISC-V GNU toolchain meeting. If you have any
topics want to
discuss or share, please let me know and I will add them to the agenda, thanks.
Agenda:
- RVV supports status
RVV calling convention to aid lazy binding
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103413
--- Comment #7 from Steve Kargl ---
On Wed, Jun 29, 2022 at 08:11:01AM +, marxin at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103413
>
> --- Comment #6 from Martin Liška ---
> (In reply to kargl from comment
1 - 100 of 175 matches
Mail list logo
