Hi Richard
Thanks for your comments.
I have updated the patch.
> -Original Message-
> From: Richard Sandiford
> Sent: Thursday, October 1, 2020 3:53 AM
> To: Qian, Jianhua/钱 建华
> Cc: gcc-patches@gcc.gnu.org
> Subject: Re: [PATCH] arm: subdivide the type attribute
> "alu_shfit_imm"
>
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97376
Bug ID: 97376
Summary: Function type to function pointer type adjustment for
non-type template paramter does not work when using
decltype(auto)
Product: gcc
On 10/11/20 6:45 PM, Martin Sebor wrote:
On 10/9/20 9:13 AM, Jason Merrill wrote:
On 10/9/20 10:51 AM, Martin Sebor wrote:
On 10/8/20 1:40 PM, Jason Merrill wrote:
On 10/8/20 3:18 PM, Martin Sebor wrote:
On 10/7/20 3:01 PM, Jason Merrill wrote:
On 10/7/20 4:11 PM, Martin Sebor wrote:
...
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97375
Bug ID: 97375
Summary: Unexpected top-level const retainment when declaring
non-type template paramter with decltype(auto)
Product: gcc
Version: unknown
Status:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97286
--- Comment #2 from Hongtao.liu ---
Seems similar issue as PR97366?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97249
--- Comment #4 from Hongtao.liu ---
(In reply to Richard Biener from comment #3)
> Guess you want to figure what built the (vec_select:V8QI (V16QI)) and if
> it was appropriately simplified (and simplify_rtx would handle this case).
> In any
Add new predicate bcst_mem_operand and corresponding constraint "Br"
to merge "$(pattern)_bcst{_1,_2,_3}" into "$(pattern)", also delete
those separate "*_bcst{_1,_2,_3}" patterns.
gcc/ChangeLog:
PR target/87767
* config/i386/constraints.md ("Br"): New special memory
Hi:
This is done in 2 steps:
1. Extend special memory constraint to handle non MEM_P cases, i.e.
(vec_duplicate:V4SF (mem:SF (addr)))
2. Refactor implementation of *_bcst{_1,_2,_3} patterns. Add new
predicate bcst_mem_operand and corresponding constraint "Br" to merge
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97374
--- Comment #2 from Martin Sebor ---
This was prompted by warnings like the one below in a build of the kernel:
drivers/gpu/drm/i915/intel_pm.c:3062:9: warning: ‘intel_print_wm_latency’
reading 16 bytes from a region of size 10
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97374
Martin Sebor changed:
What|Removed |Added
Keywords||diagnostic
--- Comment #1 from Martin
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97374
Bug ID: 97374
Summary: missing essential detail in array parameter overflow
warning
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Severity: normal
Importing them as intrinsics enables GCC to treat them as builtins
whose behavior is known by GCC.
Specifically, if they aren't intrinsics, calls to Sin and Cos won't be
combined into sincos.
We still need to make Sin and Cos wrappers inline in user-exposed
interfaces to get users the benefit
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97373
Martin Sebor changed:
What|Removed |Added
Blocks||85741
Keywords|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97373
Bug ID: 97373
Summary: missing warning on sprintf into allocated destination
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
On 10/9/20 9:13 AM, Jason Merrill wrote:
On 10/9/20 10:51 AM, Martin Sebor wrote:
On 10/8/20 1:40 PM, Jason Merrill wrote:
On 10/8/20 3:18 PM, Martin Sebor wrote:
On 10/7/20 3:01 PM, Jason Merrill wrote:
On 10/7/20 4:11 PM, Martin Sebor wrote:
...
For the various member functions, please
Snapshot gcc-11-20201011 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/11-20201011/
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=68288
--- Comment #4 from Yuriy Solodkyy ---
P.S. I added my previous example to this bug as they seemed to be related, feel
free to split it into a separate bug if they are not.
P.P.S. Change that return expression to 42_sp-p and the parser seems to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97360
Martin Sebor changed:
What|Removed |Added
Ever confirmed|0 |1
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68288
Yuriy Solodkyy changed:
What|Removed |Added
CC||solodon at mail dot com
--- Comment #3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97372
--- Comment #4 from marian ---
Running gcc under valgrind with the original testcase produces some interesting
output. These binaries of course barely have any symbols at all, but it might
at least provide a hint:
==882380== Invalid read of
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97372
--- Comment #3 from marian ---
Created attachment 49344
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=49344=edit
CVise differently reduced reproducer (possibly a different bug as well)
Attached automatically reduced reproducer does
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97372
--- Comment #2 from marian ---
Created attachment 49343
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=49343=edit
CVise reduced reproducer (possibly a different bug)
Attached testcase.ii was produced with CVise from the original
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97372
--- Comment #1 from marian ---
Created attachment 49342
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=49342=edit
pre-processed reproducer
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97372
Bug ID: 97372
Summary: Segmentation fault using Tracy 0.7.3 in template class
Product: gcc
Version: 10.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
PR libfortran/97063 - Wrong result for vector (step size is negative) * matrix
Dear all,
when matrix-multiplying rank-1 times rank-2 arrays, a wrong result was
produced when a negative stride was used for the rank-1 array. In that
case special code for rank-2 times rank-2 was erroneously
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97063
--- Comment #6 from anlauf at gcc dot gnu.org ---
Patch: https://gcc.gnu.org/pipermail/fortran/2020-October/055169.html
Hi
This corrects a typo in the recipe for the special type alignment
rules that are used for 32bit powerpc Darwin platforms.
The regression is present in all open branches (but luckily not on
7.5). I plan to fix it on the branches too.
tested across the Darwin range, and on x86_64-linux
pushed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97371
--- Comment #1 from David Binderman ---
Reduced C code is
int a, b;
void c() {
if (b >> 38)
a = b;
}
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97371
Bug ID: 97371
Summary: evrp problem with gcc.target/s390/pr77822-2.c and -O3
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97063
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |anlauf at gcc dot
On 22/09/2020 12.04, Jonathan Wakely wrote:
> On 14/09/20 16:49 +0200, Michael Weghorn via Libstdc++ wrote:
>> Hi,
>>
>> the attached patch implements pretty printers relevant for iteration
>> over std::vector, thus handling the TODO
>> added in commit 36d0dada6773d7fd7c5ace64c90e723930a3b81e
>>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97370
Harald van Dijk changed:
What|Removed |Added
CC||harald at gigawatt dot nl
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97369
--- Comment #2 from Jonathan Wakely ---
If that's a linker error not a run time error, then it looks like you're not
using the right GCC to link. It could be that you're compiling with GCC 6.3.0
but then using a different GCC to link, which
Hi
This fixes a regression present from 8.x; It used to be OK
to test for a DECL_INITIAL value to flag that an ivar was a
bitfield (the initial value was the width). This still works
on C / Objective-C, but no longer on C++. Replace the test
with DECL_C_BIT_FIELD() which is set for both C and
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97369
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
Ping.
On 2020-09-28 21:12, Alejandro Colomar wrote:
'nitems()' calculates the length of an array in number of items.
It is safe: if a pointer is passed to the macro (or function, in C++),
the compilation is broken due to:
- In >= C11: _Static_assert()
- In C89, C99: Negative anonymous
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97370
Bug ID: 97370
Summary: comedy of boolean errors for '!a & (b|c)'
Product: gcc
Version: 10.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Hi
The @selector() and @protocol() operators produce var decls
these do not work with the example plugin. Unfortunately,
unlike the ObjC front end, it is not so easy to construct a
substitute expression that works reliably. Where it does not
work we xfail for now.
tested across the Darwin
Hi
On newer systems, the throw/catch process sends retain and release
messages to thrown objects. While these are not needed in the testsuite
cases, they cause the tests to fail because the selector is not handled.
Add dummy methods to the testsuite object.
tested across the Darwin range, and
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97366
Alexander Monakov changed:
What|Removed |Added
CC||amonakov at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97369
Bug ID: 97369
Summary: undefined reference to std::_***""
Product: gcc
Version: 6.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
Hi,
Update the dg-skip to cover newer systems.
tested across the Darwin range, and on x86_64-linux
pushed to master
thanks
Iain
gcc/testsuite/ChangeLog:
* obj-c++.dg/objc-gc-3.mm:i Skip for Darwin >= 16.
---
gcc/testsuite/obj-c++.dg/objc-gc-3.mm | 2 +-
1 file changed, 1 insertion(+),
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71414
Freddie Witherden changed:
What|Removed |Added
CC||freddie at witherden dot org
---
Hi
(Darwin tests both GNU and NeXT runtimes).
The version 2 GNU Objective C API is mostly compatible with the NeXT one.
However, there are a few testsuite tweaks needed (and one test fails for NeXT
without considerable increase in complexity).
tested across the Darwin range, and on x86_64-linux
Hi
The @selector and @protocol keywords produce a var decl without
useful location information. The current diagnostics plugin does not
look at VAR_DECLs (and it would not be helpful if it did in this
case, since a single decl is shared across all the users).
However, we can, in this case, make
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96655
Dominique d'Humieres changed:
What|Removed |Added
Priority|P3 |P4
Hi,
We were using a callout to runtime.h which, eventually brings in the system
runtime.h. One newer versions of the Darwin/NeXT headers this declares the
objc_getClass() function as returning Class, rather than the internal
representation of that. This breaks a fragile assumption in objc-act
Hi
Newer versions of the runtime / NSObject don't respond to forward:.
This uses the replacement.
tested across the Darwin range, and on x86_64-linux
pushed to master
thanks
Iain
gcc/testsuite/ChangeLog:
* objc.dg/torture/forward-1.m: Implement forwarding using the
native NeXT
Hi
Older versions of the runtime don't like it when the root class
has a missing initialize method. They try to forward to an non-
existent super class resulting in a crash.
TODO: maybe we can diagnose this.
tested across the Darwin range, and on x86_64-linux
pushed to master
thanks
Iain
Hi
(Darwin tests both the GNU and NeXT runtimes)
The GNU v2 API matches the next v2 API in most respects.
However, some of the tests depend on access to items that the
later NeXT headers consider to be 'internal implementation details'
and are not exposed (we arrange that with a DEFINE).
One
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97323
Fabio changed:
What|Removed |Added
CC||pedretti.fabio at gmail dot com
--- Comment #3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97368
Fabio changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
Hi
Objective-C GC is not available for any recent Darwin version, nor
is it available for the upcoming release of Darwin20. This just updates
the skip conditions for the test.
tested across the Darwin range, and on x86_64-linux
pushed to master
thanks
Iain
gcc/testsuite/ChangeLog:
*
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97368
Fabio changed:
What|Removed |Added
Component|lto |c
--- Comment #1 from Fabio ---
>From the
Hi
Changes to deal with warnings and/or errors seen when compiling the
tests with clang (allowing us to compare a sub-set of the tests between
implementations).
tested across the Darwin range, and on x86_64-linux
pushed to master
thanks
Iain
gcc/testsuite/ChangeLog:
*
Hi
Earlier linkers cannot handle publicly-visible (or linker-visible)
metadata, so we need to make the output of these conditional on version.
tested across the Darwin range, and on x86_64-linux
pushed to master
thanks
Iain
gcc/ChangeLog:
* config/darwin.c (darwin_globalize_label):
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97368
Bug ID: 97368
Summary: randomly build failure for mesa with lto on armhf
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Hi
Newer versions of ld64 require that some meta-data symbols are
global, and that a larger set are linker-visible.
tested across the Darwin range, and on x86_64-linux
pushed to master
thanks
Iain
gcc/ChangeLog:
* config/darwin.c (darwin_globalize_label): Add protocol
meta-data
Hi
Platform compilers based on LLVM do not use the objc_sendMsg_fixit
and friends for newer editions of the OS (runtimes for Arm64 do not even
have those entries).
We need to arrange to allow for this codegen on modern Darwin.
The _fixit versions are needed for some OS versions (at least, up to
Hi,
this patch fixes the range tracking in argument and re-enables it for clones
(the bug that broke dealII and x264 benchmarks)
It turned out that there was three problems
1) for SRA/ipa-cp clones we did not update summarries to represent new
signature. This is now done in
Hi,
For current system toolchains NeXT runtime metadata symbols are not
mangled for Objective-C++ (i.e. they are considered to be
'extern "C"').
This change becomes essential when we start to emit metadata refs
as hidden and weak which is required by later editions of the runtime
and linkers.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70358
--- Comment #3 from ro at CeBiTec dot Uni-Bielefeld.DE ---
> --- Comment #2 from Jonathan Wakely ---
> Rainer, what's the status of this one? Are those tests still UNSUPPORTED, or
> now PASSing?
Looking back at old testresults, the tests were
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63332
--- Comment #11 from ro at CeBiTec dot Uni-Bielefeld.DE ---
> --- Comment #10 from Jonathan Wakely ---
> Looks like this is still failing for solaris 11:
> https://gcc.gnu.org/pipermail/gcc-testresults/2020-October/610818.html
True. However,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97367
Bug ID: 97367
Summary: powerpc64 g5 and cell optimizations result in .machine
power7
Product: gcc
Version: 10.2.0
Status: UNCONFIRMED
Severity: normal
Hi,
Make the order of the class and superclass match the metadata
order from clang. Makes it easier to compare produced meta-
data between implementations.
tested across the Darwin range and on x86_64-linux,
pushed to master
thanks
Iain
gcc/objc/ChangeLog:
* objc-next-runtime-abi-02.c
Hi
Later versions of the NeXT runtime protocol metadata contain additional
fields. This patch adds these fields and populates a new list of
method types.
tested across the range of supported Darwin systems, and on x86_64-linux
pushed to master,
thanks
Iain
gcc/objc/ChangeLog:
*
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97366
--- Comment #1 from Peter Cordes ---
Forgot to include https://godbolt.org/z/q44r13
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97366
Bug ID: 97366
Summary: [8/9/10/11 Regression] Redundant load with SSE/AVX
vector intrinsics
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Keywords:
68 matches
Mail list logo
