https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105679
--- Comment #11 from Kees Cook ---
(In reply to Richard Biener from comment #10)
> I sofar refrained from doing this because of the large amount of fallout and
> followup changes and I think those are not warranted on the GCC 12 branch.
Hi Honza,
Gentle ping
https://gcc.gnu.org/pipermail/gcc-patches/2022-September/601934.html
Thanks,
Lili.
> -Original Message-
> From: Gcc-patches On
> Behalf Of Cui, Lili via Gcc-patches
> Sent: Wednesday, September 21, 2022 5:22 PM
> To: Jan Hubicka
> Cc: Lu, Hongjiu ; Liu, Hongtao
Tested x86_64-pc-linux-gnu, applying to trunk.
-- >8 --
A discussion at Cauldron made me think that with the formalization of copy
elision in C++17, we should be able to determine before optimization which
TARGET_EXPRs will become temporaries and which are initializers. This patch
implements
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100603
Jan-Benedict Glaw changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
On Tue, 4 Oct 2022 12:03:12 -0700
Andrew Pinski via Gcc wrote:
> > Building a full distribution of this tree isn't done
> > via 'make dist'. Check out the etc/ subdirectory
...
> You just tar up the source.
> You could use maintainer-scripts/gcc_release to make a snapshot but in
>
Snapshot gcc-11-20221007 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/11-20221007/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 11 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107172
--- Comment #5 from H.J. Lu ---
i386 needs to change
(ltu:SI (const_int 1 [1])
(const_int 0 [0]))
to
(ne:SI (const_int 1 [1])
(const_int 0 [0]))
when checking the carry flag. But the mode info isn't passed to
On Fri, Oct 07, 2022 at 05:56:18PM -0400, Jason Merrill wrote:
> On 10/7/22 17:08, Marek Polacek wrote:
> > On Fri, Oct 07, 2022 at 12:17:34PM -0400, Jason Merrill wrote:
> > > On 10/6/22 22:12, Marek Polacek wrote:
> > > > On Thu, Oct 06, 2022 at 05:42:41PM -0400, Jason Merrill wrote:
> > > > >
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107085
Marek Polacek changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107085
--- Comment #11 from CVS Commits ---
The trunk branch has been updated by Marek Polacek :
https://gcc.gnu.org/g:895dd027d5dda51a95d242aec8a49a6dfa5db58d
commit r13-3173-g895dd027d5dda51a95d242aec8a49a6dfa5db58d
Author: Marek Polacek
Date:
On 10/7/22 17:08, Marek Polacek wrote:
On Fri, Oct 07, 2022 at 12:17:34PM -0400, Jason Merrill wrote:
On 10/6/22 22:12, Marek Polacek wrote:
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
On 10/7/22 17:26, Marek Polacek wrote:
On Fri, Oct 07, 2022 at 01:01:35PM -0400, Jason Merrill wrote:
On 10/7/22 12:10, Marek Polacek wrote:
On Thu, Oct 06, 2022 at 06:03:57PM -0400, Jason Merrill wrote:
On 10/6/22 17:43, Marek Polacek wrote:
On Thu, Oct 06, 2022 at 02:00:40PM -0400, Jason
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107182
--- Comment #3 from Jeffrey A. Law ---
Testing a trivial patch now.
Hi Mikael,
Am 07.10.22 um 22:26 schrieb Mikael Morin:
Le 07/10/2022 à 21:47, Mikael Morin a écrit :
Let me have a look.
The attached patch works with your test, I just moved the checks into
the loops.
I'm now checking the patch against the full fortran testsuite.
I'm (finally) fine with that
On Fri, Oct 07, 2022 at 01:01:35PM -0400, Jason Merrill wrote:
> On 10/7/22 12:10, Marek Polacek wrote:
> > On Thu, Oct 06, 2022 at 06:03:57PM -0400, Jason Merrill wrote:
> > > On 10/6/22 17:43, Marek Polacek wrote:
> > > > On Thu, Oct 06, 2022 at 02:00:40PM -0400, Jason Merrill wrote:
> > > > >
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66409
--- Comment #10 from anlauf at gcc dot gnu.org ---
(In reply to Mikael Morin from comment #7)
> I think it's in 15.4.3.4.5 Restrictions on generic declarations.
> But it's too late for me to decipher what's written there.
Tomorrow you'll
On Fri, Oct 07, 2022 at 12:17:34PM -0400, Jason Merrill wrote:
> On 10/6/22 22:12, Marek Polacek wrote:
> > 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:
> > > > >
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66409
--- Comment #9 from Mikael Morin ---
(In reply to Jeff Hammond from comment #2)
>
> My MCVE:
>
> module f
> implicit none
>
> interface test
> module procedure test_f08
> module procedure test_f08ts
> end interface
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107172
H.J. Lu changed:
What|Removed |Added
CC||hjl.tools at gmail dot com,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66409
--- Comment #8 from Steve Kargl ---
On Fri, Oct 07, 2022 at 08:42:51PM +, mikael at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66409
>
> Mikael Morin changed:
>
>What|Removed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107182
Jeffrey A. Law changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
This is notably needed because in glibc 2.34, the move of pthread functions
into libc.so happened for Linux only, not GNU/Hurd.
The pthread_self() function can also always be used fine as it is on
GNU/Hurd.
libstdc++-v3/ChangeLog:
* config/os/gnu-linux/os_defines.h [!__linux__]
Hello,
Jonathan Wakely, le ven. 07 oct. 2022 12:14:26 +0100, a ecrit:
> As documented at https://gcc.gnu.org/lists.html all patches for
> libstdc++ need to be CC'd to the libstdc++ list. That's why your patch
> has not been reviewed, because I didn't see it.
Ah, sorry, I hadn't noticed that.
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66409
Mikael Morin changed:
What|Removed |Added
CC||mikael at gcc dot gnu.org
--- Comment #7
Le 07/10/2022 à 21:47, Mikael Morin a écrit :
Let me have a look.
The attached patch works with your test, I just moved the checks into
the loops.
I'm now checking the patch against the full fortran testsuite.
I'm (finally) fine with that version, what do you think of it?From
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107183
Andrew Pinski changed:
What|Removed |Added
Component|debug |target
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66409
--- Comment #6 from anlauf at gcc dot gnu.org ---
(In reply to Steve Kargl from comment #5)
> Both match type "integer", kind "4", rank "0".
>
> AFAIK, there is no other consideration than TKR to discern which function
> to call.
Yes, assuming
Hi!
On Thu, Oct 06, 2022 at 04:29:57PM -0500, will schmidt wrote:
> 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
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66409
--- Comment #5 from Steve Kargl ---
On Fri, Oct 07, 2022 at 07:15:59PM +, anlauf at gcc dot gnu.org wrote:
>
> @Steve: I thought there is something in the standard that says how the
> resolution (specific then generic) works, but cannot
Le 07/10/2022 à 20:46, Harald Anlauf a écrit :
OK, that is because reduce_binary dispatches the reduce_binary_*.
We could move the check from reduce_binary_aa to the beginning of
reduce_binary, as with the following change on top of the patch:
diff --git a/gcc/fortran/arith.cc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66409
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |WAITING
--- Comment #4 from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100134
Patrick Palka changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107038
Siddhesh Poyarekar changed:
What|Removed |Added
Last reconfirmed||2022-10-07
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107038
--- Comment #8 from Siddhesh Poyarekar ---
I forgot to mention that I've been building with:
gcc/cc1 -o /dev/null ../bogus-stringop-overflow.i -O2 -Werror=stringop-overflow
-quiet
to reproduce the warning:
../bogus-stringop-overflow.i: In
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107038
Siddhesh Poyarekar changed:
What|Removed |Added
Summary|[13 Regression] Bogus |Bogus -Wstringop-overflow
Am 07.10.22 um 10:01 schrieb Mikael Morin:
Le 06/10/2022 à 23:36, Harald Anlauf a écrit :
For example, for this case:
[real :: 2] * [real :: +(.true.)]
First there is a "root" invocation of reduce binary with arguments [real
:: 2] and [real :: +(.true.)]
The root invocation of reduce_binary
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66409
kargl at gcc dot gnu.org changed:
What|Removed |Added
CC||kargl at gcc dot gnu.org
---
efix=/repo/gcc-trunk//binary-trunk-r13-3161-20221007142737-g89228e3985c-checking-yes-rtl-df-extra-nobootstrap-amd64
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 13.0.0 20221007 (experimental) (GCC)
FYI.
I just committed the patches to gcc13:
https://gcc.gnu.org/pipermail/gcc-cvs/2022-October/372114.html
https://gcc.gnu.org/pipermail/gcc-cvs/2022-October/372115.html
thanks.
Qing
> On Oct 6, 2022, at 8:49 AM, Qing Zhao via Gcc-patches
> wrote:
>
>
>
>> On Oct 5, 2022, at 4:25 PM,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101836
--- Comment #42 from CVS Commits ---
The master branch has been updated by Qing Zhao :
https://gcc.gnu.org/g:b9ad850e86b863c24f6f4f5acf08d49944cc7bbe
commit r13-3171-gb9ad850e86b863c24f6f4f5acf08d49944cc7bbe
Author: Qing Zhao
Date: Fri Oct
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107173
--- Comment #3 from Esa Pulkkinen ---
I realize also -E option is necessary for the problem. I tried various flags to
enable/disable modules support (e.g. -fmodules-ts), but those seem not to
impact the problem, though they impact what happens
, trunk outputs:
13.0.0 20221007
Z4mainEUlDpT_E_
-> main::{lambda((auto:1)...)#1}
So I suppose this can be resolved as fixed for GCC 13.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107181
Andrew Pinski changed:
What|Removed |Added
Component|testsuite |target
--- Comment #3 from Andrew
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107182
Andrew Pinski changed:
What|Removed |Added
Component|bootstrap |rtl-optimization
On 10/7/22 12:10, Marek Polacek wrote:
On Thu, Oct 06, 2022 at 06:03:57PM -0400, Jason Merrill wrote:
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
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55522
--- Comment #24 from H.J. Lu ---
Dropping crtfastmath.o with -shared makes sense.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54367
Bug 54367 depends on bug 102851, which changed state.
Bug 102851 Summary: Failure to demangle c++ symbol
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102851
What|Removed |Added
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102851
Patrick Palka changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97091
Patrick Palka changed:
What|Removed |Added
CC||hasse.christoph at cern dot ch
---
The _vxworks-versions.h runtime file helps us control
the compilation of some library components depending on
the OS version extracted out of a system header.
The system header name is "version.h", and gcc has a
"version.h" file of its own.
gcc's version.h is now generated and the current
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105783
David Malcolm changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
Fix a false positive from -Wanalyzer-null-dereference due to -fanalyzer
failing to grok the value of a particular boolean field initialized to a
constant.
Successfully bootstrapped & regrtested on x86_64-pc-linux-gnu.
Pushed to trunk as r13-3168-gf09b99550a3c6c.
gcc/analyzer/ChangeLog:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105783
--- Comment #2 from CVS Commits ---
The master branch has been updated by David Malcolm :
https://gcc.gnu.org/g:f09b99550a3c6cd16f5e9150ebd4b1d87033dcbd
commit r13-3168-gf09b99550a3c6cd16f5e9150ebd4b1d87033dcbd
Author: David Malcolm
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107173
--- Comment #2 from Esa Pulkkinen ---
Not sure if this info helps reproducing it, but trying to collect info about
the environment. I built gcc-13 from version
basepoints/gcc-13-2397-g20d30e737ad.
% LC_MESSAGES=C /usr/local/bin/g++ -v
Using
On 10/6/22 22:12, Marek Polacek wrote:
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
On Thu, Oct 06, 2022 at 06:03:57PM -0400, Jason Merrill wrote:
> 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:
> > > > >
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68606
--- Comment #20 from Jonathan Wakely ---
Patch posted:
https://gcc.gnu.org/pipermail/gcc-patches/2022-October/603073.html
This needs a little more documentation (see the TODO in the manual),
rather than just the comments in the source. This isn't final, but I
think it's the direction I want to take.
-- >8 --
Implement a long-standing request to support tuning the size of the
emergency buffer for allocating
On Fri, 7 Oct 2022, Nathan Sidwell wrote:
> On 10/7/22 11:09, Patrick Palka wrote:
> > According to grokbitfield, DECL_BITFIELD_REPRESENTATIVE may "temporarily"
> > contain the width of the bitfield until we layout the class type (after
> > which it'll contain a FIELD_DECL). But for a class
Antoni,
You'll want to get an employer disclaimer signed by your employer to
make sure your contributions cannot be claimed by them. Please email
ass...@fsf.org and we can work through the process.
--
All the best,
Craig Topham
Copyright & Licensing Associate
Free Software Foundation
51
> On Oct 7, 2022, at 10:43 AM, Jan Hubicka wrote:
>
Probably not hard, and the IPA pass adjusting visbility could as well
mark the functions
as not to be inlined with -flive-patching=inline-only-static.
>>
>> OTOH inline-only-static could disable WPA inlining and
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107173
Marek Polacek changed:
What|Removed |Added
CC||mpolacek at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107181
Jose E. Marchesi changed:
What|Removed |Added
CC||jose.marchesi at oracle dot com
---
On 10/7/22 11:09, Patrick Palka wrote:
According to grokbitfield, DECL_BITFIELD_REPRESENTATIVE may "temporarily"
contain the width of the bitfield until we layout the class type (after
which it'll contain a FIELD_DECL). But for a class template, it'll always
be the width since we don't/can't
On 10/7/22 08:27, Nathan Sidwell wrote:
VAR and FIELD decls can become part of a lambda context, when the
lambda is 'attached' to that entity (It's a C++20 ODR thing that was
discovered with modules, but is actually separate.) We were not
marking those decls as substitution candidates, leading
Am 2022-10-07 um 16:13 schrieb Jeff Law:
On 10/7/22 04:51, Franz Sirl wrote:
Am 2022-09-25 um 18:28 schrieb Jeff Law:
This is a minor improvement for the core_list_find routine in coremark.
Basically for riscv, and likely other targets, we can end up with an
unconditional jump to a return
According to grokbitfield, DECL_BITFIELD_REPRESENTATIVE may "temporarily"
contain the width of the bitfield until we layout the class type (after
which it'll contain a FIELD_DECL). But for a class template, it'll always
be the width since we don't/can't layout dependent types.
Tested on
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107182
--- Comment #1 from Franz Sirl ---
Created attachment 53677
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53677=edit
Related GCDA file
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107182
Bug ID: 107182
Summary: Commit
r13-2871-g1b74b5cb4e9d7191f298245063a8f9c3a1bbeff4
breaks profiledbootstrap
Product: gcc
Version: 13.0
Status:
On Thu, Oct 6, 2022 at 8:58 PM Antoni Boucher via Gcc
wrote:
> Hi.
> I contribute to gcc outside of work, but I'm about to sign a new work
> contract which contains a work ownership clause saying that I give the
> ownership to the company of any work not listed in some appendix.
>
> What exactly
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107181
seurer at gcc dot gnu.org changed:
What|Removed |Added
Host||powerpc64-linux-gnu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107181
Bug ID: 107181
Summary: new test case gcc.dg/pr25521.c fails in
r13-2952-ga0aafbc324aa90
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Wilco Dijkstra writes:
> Hi Richard,
>
>>> Yes, with a more general search loop we can get that case too -
>>> it doesn't trigger much though. The code that checks for this is
>>> now refactored into a new function. Given there are now many
>>> more calls to aarch64_bitmask_imm, I added a
> >> Probably not hard, and the IPA pass adjusting visbility could as well
> >> mark the functions
> >> as not to be inlined with -flive-patching=inline-only-static.
> >>
>
> OTOH inline-only-static could disable WPA inlining and do all inlining
> early ...
> >>>
> >>>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107176
Martin Liška changed:
What|Removed |Added
Summary|[10/11/12/13 Regression]|[10/11/12/13 Regression]
> On Oct 7, 2022, at 9:03 AM, Jan Hubicka wrote:
>
>>> WPA is Whole Program Analysis?
>>
>> Yes.
>>
>>> Okay, then It will promote all static function to extern functions. That’s
>>> reasonable.
>>
>> No, all extern functions to static functions.
>>
>>> Is it hard to preserve the
Updated patch enclosed. Changes:
* Fixes the sm >= 700 issue, I noted before (cf. below)
* The < sm_70 code is still in, but disabled at user-compile time, with a
warning, if libgomp.a wasn't compiled with sm_70 or higher. (mkoffload strips the
nvptx offload code)
* Some minor cleanup
OK
Now we have templated lambdas, we can have variadic template lambdas,
and this leads to lambda signatures containing parameter packs. But
just like 'auto' inside such a signature, we don't have a containing
template, and thus fail. The fix is to check is_lambda_arg, just as
for a template
Hi,
Whilst running a bootstrap with extra options to force bitfield
vectorization '-O2 -ftree-vectorize -ftree-loop-if-convert
-fno-vect-cost-model' I ran into an ICE in vect-patterns where a
bit_field_ref had a container that wasn't INTEGRAL_TYPE and had a
E_BLKmode, which meant we failed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106654
--- Comment #14 from Jakub Jelinek ---
Created attachment 53675
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53675=edit
gcc13-pr106654-gimple-wip.patch
My current WIP patch for the handling of more complex assumptions.
My current
On 10/6/22 01:06, Stefan Schulze Frielinghaus wrote:
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
On 10/7/22 04:51, Franz Sirl wrote:
Am 2022-09-25 um 18:28 schrieb Jeff Law:
This is a minor improvement for the core_list_find routine in coremark.
Basically for riscv, and likely other targets, we can end up with an
unconditional jump to a return statement. This is a result of
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66409
--- Comment #2 from Jeff Hammond ---
Is this ever going to be fixed? I observe that a similar MCVE (below) is
compiled without complaint by Intel, Cray and NAG Fortran, so it's almost
certainly a lack of support for the standard in GCC.
As
On Fri, Oct 07, 2022 at 09:51:31AM -0400, Jason Merrill wrote:
> > There are some tests that fail if we do that. For whatever reason,
> > they're checking the current semantics.
>
> > * gcc.dg/c11-noreturn-4.c: Add -fno-builtin-main to options.
> > * gcc.dg/inline-10.c: Likewise.
>
> IMO
On 10/7/22 07:30, Jonathan Wakely wrote:
On Tue, 4 Oct 2022 at 23:25, Jason Merrill wrote:
On 9/28/22 16:15, Jonathan Wakely wrote:
As part of implementing a C++23 proposal [1] to massively increase the
scope of the freestanding C++ standard library some questions came up
about the special
On Fri, 07 Oct 2022 05:56:39 PDT (-0700), hubi...@ucw.cz wrote:
On Fri, Oct 7, 2022 at 6:04 AM Kito Cheng 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
On 10/7/22 15:04, Qing Zhao wrote:
On Oct 7, 2022, at 2:34 AM, Richard Biener wrote:
On Thu, Oct 6, 2022 at 3:18 PM Qing Zhao wrote:
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,
I found this when reading the documentation for Kito's recent patch.
>From the discussion it sounds like this is the desired behavior, so
let's document it.
gcc/doc/ChangeLog
* invoke.texi (-falign-functions): Mention __align__
---
gcc/doc/invoke.texi | 4 +++-
1 file changed, 3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107180
Bug ID: 107180
Summary: Itanium ABI says to block in the emergency EH buffer
if memory cannot be acquired
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Hi Richard,
>> Yes, with a more general search loop we can get that case too -
>> it doesn't trigger much though. The code that checks for this is
>> now refactored into a new function. Given there are now many
>> more calls to aarch64_bitmask_imm, I added a streamlined internal
>> entry point
Hi,
On Thu, 2022-10-06 at 17:37 -0400, Siddhesh Poyarekar wrote:
> Also as I responded to Mark, the technical details of the transition are
> the responsibility of the GTI TAC (which you were invited to be member
> of and you declined) and not the LF IT, although they'd be the ones
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104433
Patrick Palka changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103524
Bug 103524 depends on bug 104433, which changed state.
Bug 104433 Summary: [modules] Importing and using std::make_shared
causes linker errors
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104433
What|Removed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104433
--- Comment #1 from CVS Commits ---
The master branch has been updated by Patrick Palka :
https://gcc.gnu.org/g:edbb2551d156d69a2e337dcd8daa69f2680d57ea
commit r13-3163-gedbb2551d156d69a2e337dcd8daa69f2680d57ea
Author: Patrick Palka
Date:
This patch stops reporting fails for Arm targets with single
precision floating point unit for types wider than 32 bits (the width
of float on arm-none-eabi).
As reported in PR102017, fenv is reported as supported in recent
versions of newlib. At the same time, for some Arm targets, the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107179
Patrick Palka changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107115
--- Comment #12 from Alexander Monakov ---
For reference, the previous whacked mole appears to be PR 106187 (where
mems_same_for_tbaa_p comes from).
Wilco Dijkstra via Gcc-patches writes:
> 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
Sorry for late reply. I just got back from vacation (a week).
I was planning to finish this patch after vacation. It seems that you almost
finished.
That's great! Thank you so much.
juzhe.zh...@rivai.ai
From: Richard Biener
Date: 2022-10-07 20:24
To: juzhe.zhong
CC: gcc-patches;
> On Oct 7, 2022, at 2:34 AM, Richard Biener wrote:
>
> On Thu, Oct 6, 2022 at 3:18 PM Qing Zhao wrote:
>>
>>
>>
>>> 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,
1 - 100 of 150 matches
Mail list logo
