On 11/6/20 8:59 PM, Jakub Jelinek wrote:
I think I'll work with Martin early next week to think about further spots
to add logging, so we narrow down where it is still called and where it
isn't.
Hello.
I'm suggesting to use the following extra logging.
Martin
>From
On Sun, 8 Nov 2020, Jan Hubicka wrote:
> Hi,
> I implemented simple propagation of EAF arguments for ipa-modref (that is not
> hard to do). My main aim was to detect cases where THIS parameter does not
> escape but is used to read/write pointed to memory. This is meant to
> avoid poor code
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80379
--- Comment #3 from Jan Hubicka ---
The problem here is that the hint is output at decl merging and
-fno-strict-aliasing is a function local flag. At that time we do not even know
what functions will be since units are not streamed in yet. This
nfo*, _stmt_vec_info*,
gimple_stmt_iterator*, _slp_tree*, _slp_instance*, int, bool,
vec*)
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-11.0.0_alpha20201108/work/gcc-11-20201108/gcc/tree-vect-loop.c:8689
0x10b8087 can_vectorize_live_stmts
/var/tmp/portage/cross-powerpc-e30
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93008
--- Comment #6 from Jan Hubicka ---
I just noticed this PR and wonder if there is anything to do on inliner side.
It uses DECL_DECLARED_INLINE that was invented to distinguish between implicit
inlines and explicit ones. So even if it would be
On Sat, 7 Nov 2020 at 00:59, Jeff Law wrote:
>
>
> On 9/18/20 6:33 AM, Christophe Lyon wrote:
> > On Thu, 17 Sep 2020 at 23:33, Jeff Law wrote:
> >>
> >> On 9/14/20 3:29 AM, Christophe Lyon via Gcc-patches wrote:
> >>> Initializing orig_err avoids a warning: "may be used uninitialized".
> >>>
>
I've noticed the following issues with the module mapper in the
-fdirectives-only mode:
1. When partially preprocessing the module interface unit, the mapper
receives the MODULE-EXPORT request that's unnecessary (BMI is not
written):
g++ ... -x c++ -E -fdirectives-only -o hello.gcm.ii
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97756
--- Comment #1 from Thomas Koenig ---
Actually, it was on a Ryzen 1700 (for the -march=native).
I'm at odds with architecture names...
Nathan Sidwell writes:
> > This doesn't seem to match the code to go into directives mode all that
> > well.? You don't reset pragma_allow_expansion or directive_line.
>
> Hm, yeah. I think neither of those fields have any bearing in
> non-directives mode, and always get set when entering
Dear:
Zeeheng manufacture here, exporting CLEAR PLASTIC CUP/PAPER BOWL/COFFEE
CUP with good quality and low price.
Call me, let’s talk details.
Rgds,
Luke.zhang
Hello All,
for new scan-assembly output resulting in use of $LC label
gcc/testsuite/ChangeLog:
* gcc.target/microblaze/others/strings1.c: Update
to include $LC label.
---
gcc/testsuite/ChangeLog | 5 +
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97705
Kewen Lin changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
Hello All,
This patch will load the DI mode immediate values from
REAL_VALUE_FROM_CONST_DOUBLE and REAL_VALUE_TO_TARGET_DOUBLE functions, as
CONST_DOUBLE_HIGH was returning the sign extension value even for the
unsigned long long constants also
gcc/ChangeLog:
*
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97759
Thomas Koenig changed:
What|Removed |Added
Keywords||missed-optimization
Hi Vladimir,
on 2020/11/6 下午10:49, Vladimir Makarov wrote:
>
> On 2020-11-06 1:15 a.m., Kewen.Lin wrote:
>> Hi,
>>
>> As PR97705 shows, my commit r11-4637 caused some dumping
>> comparison difference error on pass ira. It exposed one
>> issue about the newly introduced function
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97705
--- Comment #5 from CVS Commits ---
The master branch has been updated by Kewen Lin :
https://gcc.gnu.org/g:ce4ae1f4893e322495c5d24b2f0e807a7f7cf92f
commit r11-4827-gce4ae1f4893e322495c5d24b2f0e807a7f7cf92f
Author: Kewen Lin
Date: Sun Nov 8
> -Original Message-
> From: Richard Sandiford [mailto:richard.sandif...@arm.com]
> Sent: Tuesday, November 3, 2020 9:57 PM
> To: xiezhiheng
> Cc: gcc-patches@gcc.gnu.org
> Subject: Re: [PATCH PR94442] [AArch64] Redundant ldp/stp instructions
> emitted at -O3
>
> Thanks, I pushed both
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97760
--- Comment #1 from yangyang ---
Created attachment 49521
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=49521=edit
testcase
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97760
Bug ID: 97760
Summary: GCC outputs wrong values when compiling the testcase
with -O3
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Severity: normal
Hi,
This patch adds a new pattern in 4-insn combine. It supports the
following sign_extend(op: zero_extend, zero_extend) optimization. In the
patch, newpat is split twice. The first split becomes newi1pat and the
second becomes newi2pat. They replace i1, i2 and i3 if all of them can
be
I’m woking on TARGET_PROMOTE_FUNCTION_MODE for csky, and now there’s some
confusion.
For csky, the “POMOTE_MODE” is:
qi/hi -> si
the code is
#define PROMOTE_MODE(MODE, UNSIGNEDP, TYPE) \
if (GET_MODE_CLASS (MODE) == MODE_INT \
&& GET_MODE_SIZE (MODE) < UNITS_PER_WORD) \
The current development docs say:
>x86-64-v2
>x86-64-v3
>x86-64-v4
>
> These choices for cpu-type select the corresponding
> micro-architecture level from the x86-64 psABI. They are only available
> when compiling for an x86-64 target that uses the System V psABI.
>
> Since these cpu-type
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97759
Bug ID: 97759
Summary: Could std::has_single_bit implementation be faster?
Product: gcc
Version: 10.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
The binutils bugs seem to have been fixed.
2020-11-08 Samuel Thibault
gcc/
* config.gcc: Enable default_gnu_indirect_function in *-*-gnu*
target (but not *-*-kfreebsd*-gnu | *-*-kopensolaris*-gnu).
---
gcc/config.gcc | 4 +++-
1 file changed, 3 insertions(+), 1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97758
Bug ID: 97758
Summary: bits/std_function.h: error: unknown type name
'type_info' when using -fno-exceptions -fno-rtti
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Snapshot gcc-11-20201108 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/11-20201108/
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=97757
Iain Sandoe changed:
What|Removed |Added
Ever confirmed|0 |1
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97757
Bug ID: 97757
Summary: [11 Regression] fortran save_6.f90 fails with a segv
for -flto -O >= 2
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97756
Bug ID: 97756
Summary: Inefficient handling of 128-bit arguments
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Severity: enhancement
Priority: P3
Component:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97459
--- Comment #17 from Thomas Koenig ---
To be compilable, my previous code lacks
typedef __uint128_t mytype;
> #define ONE ((__uint128_t) 1)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97459
--- Comment #16 from Thomas Koenig ---
(In reply to Jakub Jelinek from comment #15)
> I plan to work on this early in stage3.
> And we really shouldn't use any tables, GCC should figure it all out.
> So, for double-word modulo by constant that
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97755
Harald van Dijk changed:
What|Removed |Added
CC||harald at gigawatt dot nl
--- Comment
Hello,
I would like to finally address the problem with ipa-icf being overly
conservating on memory operand equality and having overly weak hash
function. This leads to code size, compile time and compile time memory
use regressions sompared to earlier versions where we merged more
aggressively
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51242
Barry Revzin changed:
What|Removed |Added
CC||barry.revzin at gmail dot com
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97755
Bug ID: 97755
Summary: Explicit default constructor is called during
copy-list-initialization with a warning only
Product: gcc
Version: 10.2.0
Status: UNCONFIRMED
Following a recent fix on std::array this test started to fail in
_GLIBCXX_DEBUG mode.
FAIL: 23_containers/array/comparison_operators/96851.cc (test for excess
errors)
Rather than fixing it and now that __glibcxx_assert is constexpr
compatible I would like to propose to simply remove
Now that __glibcxx_assert is constexpr compatible we can do the same for
the _GLIBCXX_DEBUG equivalent.
I had also try to do the same on my own so this patch contains the
string_view tests I had written when doing so.
I plan to activate some _GLIBCXX_DEBUG checks when _GLIBCXX_ASSERTIONS
is
Hi,
I implemented simple propagation of EAF arguments for ipa-modref (that is not
hard to do). My main aim was to detect cases where THIS parameter does not
escape but is used to read/write pointed to memory. This is meant to
avoid poor code produced when we i.e. offline destructors on cold
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97589
--- Comment #3 from Thomas Koenig ---
Simplified test case:
program main
type foo
real, allocatable, dimension(:) :: a[:]
end type foo
type (foo) :: x
sync all
allocate (x%a(10)[*])
end program main
Hi
(this change reused the existing ‘class’ keyword and RID, so only
needed Objective-C context modifications).
tested on x86_64-darwin, x86_64-linux-gnu,
pushed to master,
thanks
Iain
This attribute states that a property is one manipulated by class
methods (it requires a static
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97459
--- Comment #15 from Jakub Jelinek ---
I plan to work on this early in stage3.
And we really shouldn't use any tables, GCC should figure it all out.
So, for double-word modulo by constant that would be expanded using a libcall,
go for x from the
Iain Sandoe via Gcc wrote:
Jakub Jelinek via Gcc wrote:
On Fri, Nov 06, 2020 at 08:56:25PM +0100, Richard Biener wrote:
Darwin: Darwin 20 is to be macOS 11 (Big Sur).
So, I'm afraid it must fail or bypass this code path somewhere earlier
in the hooks.
Is that maybe already known to the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97680
--- Comment #6 from Iain Sandoe ---
(In reply to Iain Sandoe from comment #5)
> I added xfail-if for powerpc-darwin (8,9, 10 and 11).
>
> https://gcc.gnu.org/pipermail/gcc-cvs/2020-November/336720.html
>
> Since i don't think I will have time
Hi
The builtin_thread_pointer test does not work for emulated TLS.
Add a target requires to cover this.
tested on x86_64-darwin, x86_64-linux-gnu
pushed to master,
Iain
gcc/testsuite/ChangeLog:
* gcc.target/i386/builtin_thread_pointer.c: Require native TLS.
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97459
--- Comment #14 from Thomas Koenig ---
Created attachment 49520
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=49520=edit
Numbers a, b so that 2^b ≡ 1 mod a up to b=64, larger b taken if several
solutions exist, plus the multiplicative
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78352
--- Comment #15 from Iain Sandoe ---
(In reply to Fabian Groffen from comment #14)
> (In reply to Eric Gallager from comment #13)
> > If we could get in touch with an actual lawyer to review which laws
> > specifically are getting in the way
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78352
--- Comment #14 from Fabian Groffen ---
(In reply to Eric Gallager from comment #13)
> If we could get in touch with an actual lawyer to review which laws
> specifically are getting in the way here, that could be helpful. I won my
> election to
47 matches
Mail list logo
