On Thu, 06 Oct 2022 21:03:25 PDT (-0700), kito.ch...@sifive.com wrote:
From: Monk Chiang
Currnetly setting of -falign-functions=N will be ignored if the function
is optimized for size or marked as cold function.
However function alignment requirement is needed even optimized for
size in some
On 10/6/22 23:50, Eugene Rozenfeld wrote:
Thank you for the review Jason.
I fixed formatting and updated the commit description:
OK.
Call statements are possible split points of a basic block so they may end up
in different basic blocks by the time
From: Monk Chiang
Currnetly setting of -falign-functions=N will be ignored if the function
is optimized for size or marked as cold function.
However function alignment requirement is needed even optimized for
size in some situations, RISC-V target is an example, RISC-V kernel implement
Thank you for the review Jason.
I fixed formatting and updated the commit description:
Call statements are possible split points of a basic block so they may end up
in different basic blocks by the time pass_ipa_auto_profile executes.
This change will also simplify
This patch to the Go frontend by Than McIntosh does some better
argument type checking for some builtin functions. This avoids a
compiler crash on cases like panic(panic("bad")). This fixes
https://go.dev/issue/56071. Bootstrapped and ran Go testsuite on
x86_64-pc-linux-gnu. Committed to
On Thu, Oct 06, 2022 at 05:42:41PM -0400, Jason Merrill wrote:
> On 10/4/22 19:06, Marek Polacek wrote:
> > On Fri, Sep 30, 2022 at 09:12:24AM -0400, Jason Merrill wrote:
> > > On 9/29/22 18:49, Marek Polacek wrote:
> > > > When getting the name of an attribute, we ought to use
> > > >
> On 6 Oct 2022, at 22:44, Jason Merrill wrote:
>
> On 10/3/22 23:53, Jason Merrill wrote:
>> On 9/30/22 18:50, Iain Sandoe wrote:
>>> Hi Jason,
>>>
On 30 Sep 2022, at 23:06, Jason Merrill wrote:
You can't use CONVERT_EXPR to convert between two class types, and it was
Hi!
On Thu, Oct 06, 2022 at 10:05:29PM +, Joseph Myers wrote:
> I'm seeing the following build failure for arc-linux-gnu after this
> commit. (Note that this is for building GCC *after* glibc, not for an
> initial inhibit_libc bootstrap build of GCC.)
>
> In file included from
>
I'm seeing the following build failure for arc-linux-gnu after this
commit. (Note that this is for building GCC *after* glibc, not for an
initial inhibit_libc bootstrap build of GCC.)
In file included from
/scratch/jmyers/glibc-bot/src/gcc/libgcc/unwind-dw2.c:413:
./md-unwind-support.h: In
On 10/6/22 17:43, Marek Polacek wrote:
On Thu, Oct 06, 2022 at 02:00:40PM -0400, Jason Merrill wrote:
On 10/6/22 13:51, Marek Polacek wrote:
On Thu, Oct 06, 2022 at 10:58:44AM -0400, Jason Merrill wrote:
On 10/6/22 10:49, Marek Polacek wrote:
On Wed, Oct 05, 2022 at 08:25:29PM -0400, Jason
On 10/3/22 23:53, Jason Merrill wrote:
On 9/30/22 18:50, Iain Sandoe wrote:
Hi Jason,
On 30 Sep 2022, at 23:06, Jason Merrill wrote:
You can't use CONVERT_EXPR to convert between two class types, and it
was
breaking copy elision.
Unfortunately, this patch breaks
My reading of the bug given as a reason for not testing that FE_INVALID is
raised for (both quiet and signaling) NaN arguments is that it's
specifically about constant arguments. That is, it ought to be possible
to have a testcase that verifies FE_INVALID is raised when appropriate
(and not
On Thu, Oct 06, 2022 at 02:00:40PM -0400, Jason Merrill wrote:
> On 10/6/22 13:51, Marek Polacek wrote:
> > On Thu, Oct 06, 2022 at 10:58:44AM -0400, Jason Merrill wrote:
> > > On 10/6/22 10:49, Marek Polacek wrote:
> > > > On Wed, Oct 05, 2022 at 08:25:29PM -0400, Jason Merrill wrote:
> > > > >
On 10/4/22 19:06, Marek Polacek wrote:
On Fri, Sep 30, 2022 at 09:12:24AM -0400, Jason Merrill wrote:
On 9/29/22 18:49, Marek Polacek wrote:
When getting the name of an attribute, we ought to use
get_attribute_name, which handles both [[ ]] and __attribute__(())
forms. Failure to do so may
Hi Mikael,
> Gesendet: Donnerstag, 06. Oktober 2022 um 22:14 Uhr
> Von: "Mikael Morin"
> An: "Harald Anlauf"
> Cc: "fortran" , "gcc-patches"
> Betreff: Re: [PATCH, v2] Fortran: error recovery for invalid types in array
> constructors [PR107000]
>
> Le 05/10/2022 à 23:40, Harald Anlauf a écrit
[PATCH, rs6000] Fix addg6s builtin with long long parameters. (PR100693)
Hi,
As reported in PR 100693, attempts to use __builtin_addg6s
with long long arguments result in truncated results.
Since the int and long long types can be coerced into each other,
(documented further near the
Hi Mikael,
I definitely agree that we need a temporary for the result of
MERGE(a,a,.true.), I just haven't found out how to do that.
The reason for the bad one-liner was that in gfc_simplify_merge
result = gfc_get_parentheses (result);
actually does have issues, in that the subsequent
Legacy VRP is calling ranger deep inside the bowels, and then trying to
copy an incompatible type. My previous patch in this area assumed that
the only possibility out of vr_values::get_value_range for an
unsupported type was VARYING, but UNDEFINED can also be returned.
PR
Le 06/10/2022 à 10:37, Mikael Morin a écrit :
Le 05/10/2022 à 22:40, Harald Anlauf a écrit :
Hi Mikael,
Gesendet: Mittwoch, 05. Oktober 2022 um 12:34 Uhr
Von: "Mikael Morin"
Please move the check to resolve_transfer in resolve.cc.
I have done this, see attached updated patch.
Regtests
Le 05/10/2022 à 23:40, Harald Anlauf a écrit :
There is one last thing that I'm dissatisfied with.
The handling of unknown types should be moved to reduce_binary, because
the dispatching in reduce_binary doesn't handle EXPR_OP, so even if
either or both operands are scalar, they are handled by
Successfully bootstrapped & regrtested on x86_64-pc-linux-gnu.
Pushed to trunk as r13-3137-g30d6356773a838.
gcc/analyzer/ChangeLog:
* call-summary.cc (call_summary_replay::dump_to_pp): Bulletproof
against NULL caller regions/svalues.
Signed-off-by: David Malcolm
---
I overreduced PR analyzer/107158 in r13-3096-gef878564140cbc, and there
was another ICE in the original reproducer, which this patch fixes.
Successfully bootstrapped & regrtested on x86_64-pc-linux-gnu.
Pushed to trunk as r13-3138-g629b4813e91aba.
gcc/analyzer/ChangeLog:
PR
`basic_filebuf::xsputn` would bypass the buffer when passed a chunk of
size 1024 and above, seemingly as an optimisation.
This can have a significant performance impact if the overhead of a
`write` syscall is non-negligible, e.g. on a slow disk, on network
filesystems, or simply during IO
On 10/6/22 14:29, Jakub Jelinek wrote:
On Thu, Oct 06, 2022 at 01:30:18PM -0400, Jason Merrill wrote:
Yes, except I was thinking the new function would take the attribute
TREE_LIST as its parameter so that all the callers don't have to also call
get_attribute_namespace.
Ok, here it is in
On Thu, Oct 06, 2022 at 01:30:18PM -0400, Jason Merrill wrote:
> Yes, except I was thinking the new function would take the attribute
> TREE_LIST as its parameter so that all the callers don't have to also call
> get_attribute_namespace.
Ok, here it is in patch form.
2022-10-06 Jakub Jelinek
Tested x86_64-pc-linux-gnu, OK for trunk?
-- >8 --
In this testcase, we were optimizing away the temporary for f(), but
C++17 and above are clear that there is a temporary, and because its
destructor has visible side-effects we can't optimize it away under the
as-if rule. So disable this
On 10/6/22 13:51, Marek Polacek wrote:
On Thu, Oct 06, 2022 at 10:58:44AM -0400, Jason Merrill wrote:
On 10/6/22 10:49, Marek Polacek wrote:
On Wed, Oct 05, 2022 at 08:25:29PM -0400, Jason Merrill wrote:
On 10/5/22 17:27, Marek Polacek wrote:
This PR reports that
struct Base {};
On Thu, Oct 06, 2022 at 10:58:44AM -0400, Jason Merrill wrote:
> On 10/6/22 10:49, Marek Polacek wrote:
> > On Wed, Oct 05, 2022 at 08:25:29PM -0400, Jason Merrill wrote:
> > > On 10/5/22 17:27, Marek Polacek wrote:
> > > > This PR reports that
> > > >
> > > > struct Base {};
> > > >
Hi
Looks like the previous patch was not enough. When using it in the
context of a build without dual abi and versioned namespace I started
having failures again. I guess I hadn't rebuild everything properly.
This time I think the problem was in those lines:
if self.type_obj ==
On 10/6/22 10:34, Paul Iannetta wrote:
Hi,
Presently, GCC supports target address spaces as a GNU extension (cf.
`info -n "(gcc)Named Address Spaces"`). This is however supported
only by the C frontend, which is a bit sad, since all the GIMPLE
machinery is readily available and, moreover, LLVM
On 10/6/22 13:20, Jakub Jelinek wrote:
On Thu, Oct 06, 2022 at 09:42:47AM -0400, Jason Merrill wrote:
- tree t = lookup_attribute ("fallthrough", attr);
+ tree t = lookup_attribute (NULL, "fallthrough", attr);
+ if (t == NULL_TREE)
+t = lookup_attribute ("gnu", "fallthrough", attr);
Hi Richard,
> Did you consider handling the case where the movks aren't for
> consecutive bitranges? E.g. the patch handles:
> but it looks like it would be fairly easy to extend it to:
>
> 0x12345678
Yes, with a more general search loop we can get that case too -
it doesn't trigger
Hi,
even at -O0 there may be a fair amount of DF computation performed when
compiling large units and part of it appears to be useless.
Bootstrapped/regtested on x86-64/Linux, OK for the mainline?
2022-10-06 Eric Botcazou
* function.cc (thread_prologue_and_epilogue_insns): Update
On Thu, Oct 06, 2022 at 09:42:47AM -0400, Jason Merrill wrote:
> > - tree t = lookup_attribute ("fallthrough", attr);
> > + tree t = lookup_attribute (NULL, "fallthrough", attr);
> > + if (t == NULL_TREE)
> > +t = lookup_attribute ("gnu", "fallthrough", attr);
>
> Maybe lookup_attribute
On Thu, 6 Oct 2022 at 17:33, Charles-François Natali
wrote:
>
> On Thu, Oct 6, 2022, 14:29 Jonathan Wakely wrote:
>>
>> Sorry for the lack of review. I've been trying to remember (and find)
>> some previous discussions related to this topic, but haven't managed
>> to find it yet.
>
>
> No
> On 6 Oct 2022, at 14:17, Richard Biener wrote:
>>
>> Ok to commit?
>
> OK.
Thanks!
> On 6 Oct 2022, at 14:15, Richard Biener wrote:
>
>> Is this ok to commit?
>
> I think this is reasonable, thus OK.
Great, thanks Richard :-)
On Thu, Oct 6, 2022, 14:29 Jonathan Wakely wrote:
> Sorry for the lack of review. I've been trying to remember (and find)
> some previous discussions related to this topic, but haven't managed
> to find it yet.
>
No worries!
> The patch does look sensible (and is the same as the one attached
On Thu, Oct 06, 2022 at 06:15:52PM +0200, Tobias Burnus wrote:
> On 06.10.22 14:17, Jakub Jelinek wrote:
> > On Thu, Oct 06, 2022 at 12:55:01PM +0200, Tobias Burnus wrote:
> > > I don't know whether it makes sense to handle – in the long run – the
> > > case of se.pre/se.post being nonempty – and,
The below testcase fails to link with the error
undefined reference to `f()::y'
ultimately because during stream out for the static VAR_DECL y we
override DECL_EXTERNAL to true, which later during IPA confuses
symbol_table::remove_unreachable_nodes into thinking it's safe
to not emit the
On 06.10.22 14:17, Jakub Jelinek wrote:
On Thu, Oct 06, 2022 at 12:55:01PM +0200, Tobias Burnus wrote:
I don't know whether it makes sense to handle – in the long run – the
case of se.pre/se.post being nonempty – and, if so, how.
I think it is essential not to throw those away,
if se.pre or
Source: gcc-12
Version: 12_12.2.0-5
Severity: important
Tags: patch
User: debian-h...@lists.debian.org
Usertags: hurd
Affects: gcc-11, gcc-snapshot
X-Debbugs-CC: debian-h...@lists.debian.org
Hi,
gcc-12-12.2.0-4/5 in sid FTBFS on hurd-i386 due to failing linkage of
pthread_once (same error for
On 10/6/22 10:49, Marek Polacek wrote:
On Wed, Oct 05, 2022 at 08:25:29PM -0400, Jason Merrill wrote:
On 10/5/22 17:27, Marek Polacek wrote:
This PR reports that
struct Base {};
struct Derived : Base {};
static_assert(__reference_constructs_from_temporary(Base const&, Derived));
On Wed, Oct 05, 2022 at 08:25:29PM -0400, Jason Merrill wrote:
> On 10/5/22 17:27, Marek Polacek wrote:
> > This PR reports that
> >
> >struct Base {};
> >struct Derived : Base {};
> >static_assert(__reference_constructs_from_temporary(Base const&,
> > Derived));
> >
> > doesn't
Hi,
Presently, GCC supports target address spaces as a GNU extension (cf.
`info -n "(gcc)Named Address Spaces"`). This is however supported
only by the C frontend, which is a bit sad, since all the GIMPLE
machinery is readily available and, moreover, LLVM supports this GNU
extension both for C
On 06/10/2022 10:12, Richard Biener wrote:
> On Wed, Oct 5, 2022 at 2:49 PM Martin Liška wrote:
>>
>> On 10/5/22 14:04, Jørgen Kvalsvik via Gcc-patches wrote:
>>> Edges with locus are candidates for splitting so that the edge with
>>> locus is the only edge out of a basic block, except when the
On 10/5/22 08:04, Jakub Jelinek wrote:
Hi!
The following patch uses the new lookup_attribute overload and extra
tests to avoid emitting weird warnings on foreign namespace attributes
which we should just ignore (perhaps with a warning), but shouldn't
imply any meaning to them just because they
Sorry for the lack of review. I've been trying to remember (and find)
some previous discussions related to this topic, but haven't managed
to find it yet.
The patch does look sensible (and is the same as the one attached to
PR 63746) so I'll make sure to review it in time for the GCC 13
cut-off.
On Thu, Sep 22, 2022, 17:51 Charles-François Natali
wrote:
>
> On Mon, Sep 5, 2022, 23:51 Charles-Francois Natali
> wrote:
>
>> `basic_filebuf::xsputn` would bypass the buffer when passed a chunk of
>> size 1024 and above, seemingly as an optimisation.
>>
>> This can have a significant
> On Oct 6, 2022, at 4:29 AM, Richard Biener wrote:
>
> On Wed, Oct 5, 2022 at 8:18 PM Qing Zhao via Gcc-patches
> wrote:
>>
>>
>>
>>> On Oct 5, 2022, at 1:36 PM, Martin Liška wrote:
>>>
>>> On 10/5/22 16:50, Qing Zhao wrote:
I have two questions on this:
>>>
>>> Hello.
>>>
On Thu, Oct 6, 2022 at 2:13 PM Richard Biener
wrote:
>
> On Fri, Sep 30, 2022 at 10:00 AM wrote:
> >
> > From: Ju-Zhe Zhong
> >
> > Hi, After fixing previous ICE.
> > I add full implementation (insert permutation to get correct result.)
> >
> > The gimple IR is correct now I think:
> > # t_21
> On Oct 5, 2022, at 4:25 PM, Joseph Myers wrote:
>
> On Wed, 5 Oct 2022, Qing Zhao via Gcc-patches wrote:
>
>> + /* if not the last field, return false. */
>
> Comments should start with an uppercase letter.
>
>> + /* if not an array field, return false. */
>
>> + /* if there is a
On Thu, Oct 6, 2022 at 1:09 PM Eric Botcazou wrote:
>
> > I'm wondering if testing DR_IS_WRITE (dra) is enough here and whether
> > the logic also applies to RAW and WAR. So should it be either
> > (DR_IS_WRITE (dra) || DR_IS_WRITE (drb)) or DR_IS_WRITE (dra) &&
> > DR_IS_WRITE (drb) instead?
>
The following preserves the (premature) redundant store removal
done in store_expr by appropriately guarding it with
mems_same_for_tbaa_p. The testcase added needs scheduling disabled
for now since there's a similar bug there still present.
Bootstrapped and tested on x86_64-unknown-linux-gnu,
On Fri, Sep 30, 2022 at 6:35 PM Olivier Hainque via Gcc-patches
wrote:
>
> Hello,
>
> The attached patch is a proposal to #undef offsetof before
> the #define we do in ginclude/stddef.h, which prevents redefinition
> warnings from dg tests passing -Wsystem-headers on systems which
> provide a
On Thu, Oct 06, 2022 at 12:55:01PM +0200, Tobias Burnus wrote:
> Same as for C/C++, albeit a tiny bit longer patch.
>
> I don't know whether it makes sense to handle – in the long run – the
> case of se.pre/se.post being nonempty – and, if so, how.
I think it is essential not to throw those
On Fri, Sep 30, 2022 at 6:18 PM Olivier Hainque via Gcc-patches
wrote:
>
> Hello,
>
> This change is a proposal to introduce a target overridable macro
> to replace the hardcoded value used in common.opt to initialize
> dwarf_version.
>
> The main advantage compared to special code in a target
>
On Fri, Sep 30, 2022 at 10:00 AM wrote:
>
> From: Ju-Zhe Zhong
>
> Hi, After fixing previous ICE.
> I add full implementation (insert permutation to get correct result.)
>
> The gimple IR is correct now I think:
> # t_21 = PHI <_4(6), t_12(9)>
> # i_22 = PHI
> # vectp_a.6_26 = PHI
> #
Hi all,
Like other loads in AArch64, the LDARB,LDARH,LDAR instructions clear out the
top part of their
destination register and we can thus avoid having to explicitly zero-extend it.
We were missing a combine pattern that this patch adds.
For one of the examples in the testcase we generated:
Hi all,
I'd like a test to check the generation of LDAR for atomic_load_n.
No new functionality added.
Pushing to trunk.
Thanks,
Kyrill
gcc/testsuite/ChangeLog:
* gcc.target/aarch64/ldar_1.c: New test.
ldar-test.patch
Description: ldar-test.patch
> I'm wondering if testing DR_IS_WRITE (dra) is enough here and whether
> the logic also applies to RAW and WAR. So should it be either
> (DR_IS_WRITE (dra) || DR_IS_WRITE (drb)) or DR_IS_WRITE (dra) &&
> DR_IS_WRITE (drb) instead?
It's a self-dependence, i.e. dra == drb in the block. Or do you
Same as for C/C++, albeit a tiny bit longer patch.
I don't know whether it makes sense to handle – in the long run – the
case of se.pre/se.post being nonempty – and, if so, how.
OK for mainline?
Tobias
-
Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201,
This is the op1_range range-op entry for __builtin_signbit. It allows
us to wind back through a call to signbit.
For example, on the true side of if (__builtin_signbit(x_5) != 0) we
can crop down the range of x_5 to:
[frange] float [-Inf, -0.0 (-0x0.0p+0)] -NAN
Similarly on the false
Applied to master. Thanks!
Philipp.
On Thu, 6 Oct 2022 at 12:07, Richard Sandiford
wrote:
> Philipp Tomsich writes:
> > This brings the extensions detected by -mcpu=native on Ampere-1 systems
> > in sync with the defaults generated for -mcpu=ampere1.
> >
> > Note that some early kernel
On Thu, 6 Oct 2022 at 12:06, Richard Sandiford
wrote:
> Philipp Tomsich writes:
> > Fixes: 341573406b39
> >
> > Don't subtract one from the result of strnlen() when trying to point
> > to the first character after the current string. This issue would
> > cause individual characters (where the
Philipp Tomsich writes:
> This brings the extensions detected by -mcpu=native on Ampere-1 systems
> in sync with the defaults generated for -mcpu=ampere1.
>
> Note that some early kernel versions on Ampere1 may misreport the
> presence of PAUTH and PREDRES (i.e., -mcpu=native will add 'nopauth'
>
The following fixes an unintended(?) side-effect of the special
MODIFY_EXPR expression entries we add for tail-merging during VN.
We shouldn't value-number the virtual operand differently here.
Bootstrapped and tested on x86_64-unknown-linux-gnu, pushed.
PR tree-optimization/107107
Philipp Tomsich writes:
> Fixes: 341573406b39
>
> Don't subtract one from the result of strnlen() when trying to point
> to the first character after the current string. This issue would
> cause individual characters (where the 128 byte buffers are stitched
> together) to be lost.
>
>
From: Eric Botcazou
It is based on a new LOAD_EXPR node in GENERIC that is later turned into
a bona-fide temporary during gimplification.
gcc/ada/
* gcc-interface/ada-tree.def (LOAD_EXPR): New expression code.
* gcc-interface/gigi.h (build_storage_model_load): Declare.
From: Steve Baird
In sem_ch6.adb, the procedure Analyze_Procedure_Call is preceded with a
comment:
-- WARNING: This routine manages Ghost regions. Return statements must be
-- replaced by gotos that jump to the end of the routine and restore the
-- Ghost mode.
Correct a violation of
From: Piotr Trojanek
In lock-free protected subprograms we don't allow goto statements;
likewise, we now reject conditional goto statements.
This fix only affects semantic checking mode with switch -gnatc.
In ordinary compilation we already rejected conditional goto after
it was expanded into
From: Alexandre Oliva
gcc/ada/
* doc/gnat_rm/security_hardening_features.rst: Add examples of
codegen changes in stack scrubbing.
* gnat_rm.texi: Regenerate.
Tested on x86_64-pc-linux-gnu, committed on master.
---
.../gnat_rm/security_hardening_features.rst | 52
From: Piotr Trojanek
Cleanup code and documentation; semantics is unaffected.
gcc/ada/
* doc/gnat_rm/implementation_defined_pragmas.rst
(Lock_Free): Remove inconsistent periods that end item
descriptions.
* sem_ch9.adb
(Allows_Lock_Free_Implementation):
From: Alexandre Oliva
gcc/ada/
* doc/gnat_rm/security_hardening_features.rst: Add examples of
codegen changes in hardened conditionals.
* gnat_rm.texi: Regenerate.
Tested on x86_64-pc-linux-gnu, committed on master.
---
.../gnat_rm/security_hardening_features.rst |
From: Alexandre Oliva
Show the sort of code that is to be expected from using hardened
booleans in Ada code. Mention that C traps instead of raising
exceptions.
gcc/ada/
* doc/gnat_rm/security_hardening_features.rst: Add examples of
codegen changes in hardened booleans.
This brings the extensions detected by -mcpu=native on Ampere-1 systems
in sync with the defaults generated for -mcpu=ampere1.
Note that some early kernel versions on Ampere1 may misreport the
presence of PAUTH and PREDRES (i.e., -mcpu=native will add 'nopauth'
and 'nopredres').
gcc/ChangeLog:
Add needed C declarations for Storage Model support in gigi.
gcc/ada/
* fe.h (Has_Storage_Model_Type_Aspect)
(Has_Designated_Storage_Model_Aspect, Storage_Model_Object)
(Storage_Model_Copy_From, Storage_Model_Copy_To): Add
declarations.
* sem_util.ads: Add
From: Piotr Trojanek
Validity checks for statements in a lock-free implementation of
protected subprogram were wrongly inserted in front of the original
statements. This happened because the lock-free implementation was
created as a shallow copy, where only the protected body statements were
From: Steve Baird
Within the first (respectively, second) statement list of this if statement
declare
X : constant Integer := ... ;
begin
if X > 0 then
...;
else
...;
end if;
end;
we can safely assume that X is greater (respectively, not greater) than 0.
From: Gary Dismukes
The compiler was wrongly reporting an error on a function call within
a Pre'Class expression when a formal of the aspect's subprogram was
passed to an aliased formal. This occurred due to the call appearing
with the return statement of the wrapper function created for the
Fixes: 341573406b39
Don't subtract one from the result of strnlen() when trying to point
to the first character after the current string. This issue would
cause individual characters (where the 128 byte buffers are stitched
together) to be lost.
gcc/ChangeLog:
*
From: Bob Duff
In the recursive case of Volatile_Or_Independent = False for array
types, fall through into later checks, so for example we check
the type of the prefix of a slice. The pattern here is "return True
in certain cases, otherwise fall through into the final 'return False'".
Remove
From: Yannick Moy
Use of pragma Warning with a string literal to set warning
switches, should not impact GNATprove which is not subject
to these switches.
gcc/ada/
* sem_prag.adb (Analyze_Pragma): Ignore one variant of pragma
Warnings in GNATprove mode.
Tested on
From: Bob Duff
This patch disables the Fast_Copy_Bitfield optimization in certain rare
cases that currently do not work (crash in gigi). We could improve
Expand_Assign_Array_Bitfield_Fast to handle these cases properly, but
that change is delicate, so for now, we simply disable the optimization.
From: Piotr Trojanek
Listing an object as a state refinement constituent shouldn't be
considered to be a reference, at least from the point of view of the
machinery for detecting objects that are never referenced or written
without being referenced.
This patch fixes a spurious warning that
On Tue, 4 Oct 2022 at 18:43, Richard Sandiford
wrote:
>
> Philipp Tomsich writes:
> > This brings the extensions detected by -mcpu=native on Ampere-1 systems
> > in sync with the defaults generated for -mcpu=ampere1.
> >
> > Note that some kernel versions may misreport the presence of PAUTH and
On 10/5/22 22:09, Tobias Burnus wrote:
> On 05.10.22 20:41, Martin Liška wrote:
>> +++ b/contrib/gcc-changelog/git_update_version.py
>> @@ -127,6 +127,7 @@ def update_current_branch(ref_name):
>> repo.git.add(datestamp_path)
>> if not args.current:
>>
Max page size is defined in the ARC's BFD file, and the common page
size is also set by the appropriate binutils macros. Remove them from
LINK_SPEC.
2022-10-06 Claudiu Zissulescu
* config/arc/linux.h (LINK_SPEC): Remove max-page-size and
common-pave-size.
Signed-off-by:
Hi!
Now that [[assume (cond)]] support is in, this simple patch makes
#pragma omp assume holds(cond)
use it.
Committed to trunk.
2022-10-06 Jakub Jelinek
* c-parser.cc (c_parser_omp_assumption_clauses): Emit IFN_ASSUME
call for holds clause on assume construct.
*
ping*3
please?
> Le 21 sept. 2022 à 11:40, FX a écrit :
>
> ping*2
>
> <0001-Add-__builtin_iseqsig.patch>
>
>> Le 9 sept. 2022 à 19:55, FX a écrit :
>>
>> ping
>>
>>
>>> Le 1 sept. 2022 à 23:02, FX a écrit :
>>>
>>> Attached patch adds __builtin_iseqsig() to the middle-end and C family
On 10/6/22 10:29, Richard Biener wrote:
> On Wed, Oct 5, 2022 at 8:18 PM Qing Zhao via Gcc-patches
> wrote:
>>
>>
>>
>>> On Oct 5, 2022, at 1:36 PM, Martin Liška wrote:
>>>
>>> On 10/5/22 16:50, Qing Zhao wrote:
I have two questions on this:
>>>
>>> Hello.
>>>
1. What’s the
Le 05/10/2022 à 22:40, Harald Anlauf a écrit :
Hi Mikael,
Gesendet: Mittwoch, 05. Oktober 2022 um 12:34 Uhr
Von: "Mikael Morin"
Please move the check to resolve_transfer in resolve.cc.
I have done this, see attached updated patch.
Regtests cleanly on x86_64-pc-linux-gnu.
Strangely, the
On Thu, Oct 6, 2022 at 3:22 AM Joseph Myers wrote:
>
> [C++ maintainers / global reviewers, note that there is a C++
> front-end change here needing review.]
>
> C2x adds typeof as a standard feature. In general this follows
> existing GNU C semantics very closely, but there are various ways in
On Wed, Oct 5, 2022 at 8:18 PM Qing Zhao via Gcc-patches
wrote:
>
>
>
> > On Oct 5, 2022, at 1:36 PM, Martin Liška wrote:
> >
> > On 10/5/22 16:50, Qing Zhao wrote:
> >> I have two questions on this:
> >
> > Hello.
> >
> >>
> >> 1. What’s the motivation to enable -flive-patching with -flto? Is
On Jun 28, 2022, Alexandre Oliva wrote:
> Support multilib-aware target lib flags self-specs overriding
> This patch introduces -fmultiflags, short for multilib TFLAGS, as an
> option that does nothing by default, but that can be added to TFLAGS
> and mapped to useful options by driver
On Wed, Oct 5, 2022 at 5:39 PM Eric Botcazou via Gcc-patches
wrote:
>
> Hi,
>
> as shown by the attached testcase, there is a loophole in the unroll-and-jam
> pass that can quickly result in wrong code generation. The code reads:
>
> if (!compute_data_dependences_for_loop (outer, true,
On Wed, Oct 5, 2022 at 2:49 PM Martin Liška wrote:
>
> On 10/5/22 14:04, Jørgen Kvalsvik via Gcc-patches wrote:
> > Edges with locus are candidates for splitting so that the edge with
> > locus is the only edge out of a basic block, except when the locuses
> > match. The test checks the last
On Wed, Oct 5, 2022 at 12:34 PM Jakub Jelinek via Gcc-patches
wrote:
>
> Hi!
>
> I'd like to ping this patch.
The patch is OK.
Richard.
> Thanks.
>
> > 2022-09-19 Jakub Jelinek
> >
> > * unwind-dw2.h (REG_UNSAVED, REG_SAVED_OFFSET, REG_SAVED_REG,
> > REG_SAVED_EXP,
On Wed, 5 Oct 2022, Kyrylo Tkachov wrote:
>
>
> > -Original Message-
> > From: Andre Vieira (lists)
> > Sent: Tuesday, October 4, 2022 11:34 AM
> > To: Kyrylo Tkachov ; gcc-patches@gcc.gnu.org;
> > Richard Sandiford ; Richard Biener
> >
> > Subject: Re: [PATCH][AArch64] Implement ACLE
On Wed, Oct 05, 2022 at 08:48:13PM -0600, Jeff Law via Gcc-patches wrote:
>
> On 10/4/22 05:28, Stefan Schulze Frielinghaus via Gcc-patches wrote:
> > For BImode get_narrowest_mode evaluates to QImode but BImode < QImode.
> > Thus FOR_EACH_MODE_UNTIL never reaches BImode and iterates until OImode
1 - 100 of 103 matches
Mail list logo
