https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104986
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100545
--- Comment #3 from Jason Merrill ---
Created attachment 52829
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52829=edit
fix
The "ftree-parallelize-loops=" imply -pthread option in gcc/gcc.cc,
some target are not support pthread like elf target use newlib,
and will get an error:
"*-*-elf-gcc: error: unrecognized command-line option '-pthread'"
so we add an additional condition "{target pthread}" to make sure the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105101
--- Comment #11 from Michael_S ---
(In reply to Michael_S from comment #10)
> BTW, the same ideas as in the code above could improve speed of division
> operation (on modern 64-bit HW) by factor of 3 (on Intel) or 2 (on AMD).
Did it.
On Intel
Also available through the wayback machine, but only a valid
currently-working URL is appropriate on that page, IMHO.
Thanks to Paul Koning for finding it.
---
htdocs/readings.html | 1 +
1 file changed, 1 insertion(+)
diff --git a/htdocs/readings.html b/htdocs/readings.html
index
On Fri, Apr 15, 2022 at 6:38 AM Sören Tempel wrote:
>
> Attached are two small git-format-patch(1) files which add support for
> musl libc to gofrontend's mksigtab.sh script. They address the following
> issues:
>
> * Signal 34 is special on musl and is used internally for
>
If two arrays do not have the exact same element type including qualification,
this could be e.g. f(int (&&)[]) vs. f(int const (&)[]), which can still be
distinguished by the lvalue-rvalue tiebreaker.
By tightening this branch (in accordance with the letter of the Standard) we
fall through to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105302
--- Comment #4 from Ian Lance Taylor ---
> What exactly would be the file(s) being opened in this case?
The file that should be opened is the file internal/cpu.gox in the libgo build
directory.
> When can we expect the libgo cleanup needed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105302
--- Comment #3 from Brecht Sanders
---
What exactly would be the file(s) being opened in this case?
When can we expect the libgo cleanup needed for MinGW(-w64) support?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105302
--- Comment #2 from Ian Lance Taylor ---
I have no idea why you would get a "Permission denied" error opening an import
package.
That said I would not expect this to work. Somebody would have to clean up
libgo to support Windows.
Gentle ping :)
Link: https://gcc.gnu.org/pipermail/gcc-patches/2022-April/592685.html
The series adds support for new attribues btf_type_tag and btf_decl_tag,
for recording arbitrary string tags in DWARF and BTF debug info. The
feature is to support kernel use cases.
Thanks,
David
On
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104981
--- Comment #1 from Iain Sandoe ---
the coroutines code appears to be passing reasonable input to the CTOR build
call.
coroutines.cc:4922:
r = build_special_member_call (p, complete_ctor_identifier, NULL,
On Mon, 18 Apr 2022, 15:39 Patrick Palka via Libstdc++, <
libstd...@gcc.gnu.org> wrote:
> At the first iteration of __from_chars_pow2_base's main loop, we need
> to remember the value of the leading significant digit for sake of the
> overflow check at the end of the function (for bases other
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104981
Iain Sandoe changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103963
Iain Sandoe changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98056
Iain Sandoe changed:
What|Removed |Added
CC||me at xecycle dot info
--- Comment #18
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104020
Iain Sandoe changed:
What|Removed |Added
CC||iains at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105104
Iain Sandoe changed:
What|Removed |Added
Last reconfirmed|2022-03-30 00:00:00 |2022-4-18
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105289
Patrick Palka changed:
What|Removed |Added
Known to fail||11.2.0, 12.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103662
--- Comment #13 from Mikael Morin ---
(In reply to Mikael Morin from comment #12)
> ... so I must be missing important.
I must be missing *something* important.
Hi,
Wilco pointed out in https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105162#c7?
that
"Only __sync needs the extra full barrier, but __atomic does not."
The attached patch does that by adding out-of-line functions for
MEMMODEL_SYNC_*.
Those new functions contain a barrier on the path
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103662
Mikael Morin changed:
What|Removed |Added
CC||mikael at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105293
--- Comment #5 from Elmar Stellnberger ---
Created attachment 52827
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52827=edit
2nd version of patch that should be useable under gcc-8-8.3.0/debian/patches/
Last time I reported that I
Also adjust DejaGnu directives, as specifically requiring "powerpc*-*-*" is no
longer required.
2021-04-18 Paul A. Clarke
gcc/testsuite
* g++.dg/pr65240.h: Move to g++.target/powerpc.
* g++.dg/pr93974.C: Likewise.
* g++.dg/pr65240-1.C: Move to g++.target/powerpc,
A few tests need not be restricted to 'lp64', so remove the restriction.
A few of those need a simple change to the DejaGnu directives to suppress
'-mcmodel' flags for '-m32'.
2022-04-18 Paul A. Clarke
gcc/testsuite
* g++.target/powerpc/pr65240-1.C: Adjust DejaGnu directives.
v3: moved "not tested on Darwin" changes into 1/2, where they belong.
v2:
- v1 patches 1/3 and 2/3 have been merged after reviews / approval.
- Previous 3/3 is now 1/2, and new 2/2 is per review from Segher...
Some tests in g++.dg are target-specific for powerpc. Move those to
> From: Hans-Peter Nilsson
> gcc:
> * doc/install.texi : Remove references to removed websites and
> adjust for cris-*-elf being the only remaining toolchain.
Oops, cutnpasto for the ChangeLog entry. :(
This one fits better:
* doc/invoke.texi : Remove references to options
I'm about to commit this to master.
I'd like to also install this on the gcc-11 branch.
Ok?
-- 8< --
...and related options. These stale bits were overlooked when support
for "Linux/GNU" and CRIS v32 was removed, before the gcc-11 release.
Resulting pdf, html and info inspected for sanity.
Also adjust DejaGnu directives, as specifically requiring "powerpc*-*-*" is no
longer required.
2021-04-18 Paul A. Clarke
gcc/testsuite
* g++.dg/pr65240.h: Move to g++.target/powerpc.
* g++.dg/pr93974.C: Likewise.
* g++.dg/pr65240-1.C: Move to g++.target/powerpc,
A few tests need not be restricted to 'lp64', so remove the restriction.
A few of those need a simple change to the DejaGnu directives to suppress
'-mcmodel' flags for '-m32'.
2022-04-18 Paul A. Clarke
gcc/testsuite
* g++.target/powerpc/pr65240-1.C: Adjust DejaGnu directives.
V1 patches 1/3 and 2/3 have been merged after reviews / approval.
Previous 3/3 is now 1/2, and new 2/2 is per review from Segher...
Some tests in g++.dg are target-specific for powerpc. Move those to
g++.target/powerpc. Update the DejaGnu directives as needed, since
the target restriction is
I'm about to commit this to master.
I'd like to also install this on the gcc-11 branch.
Ok?
-- 8< --
That is, support for cris-linux-gnu was removed in gcc-11, but
install.texi wasn't adjusted accordingly. Also, unfortunately the
developer-related sites are gone with no replacements. And,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105304
Bug ID: 105304
Summary: ICE segfault using ad-hoc concept with -Wall
Product: gcc
Version: 11.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
Unfortunately I know of no replacement.
---
htdocs/readings.html | 1 -
1 file changed, 1 deletion(-)
diff --git a/htdocs/readings.html b/htdocs/readings.html
index 8689eab8b2d1..2467945b1cb6 100644
--- a/htdocs/readings.html
+++ b/htdocs/readings.html
@@ -118,7 +118,6 @@ names.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104051
Iain Sandoe changed:
What|Removed |Added
Last reconfirmed||2022-04-18
Assignee|unassigned
We check that the final_suspend () method returns a sane type (i.e. a class
or structure) but, unfortunately, that check has to be later than the one
for a throwing case. If the user returns some nonsensical type from the
method, we need to handle that in the checking for noexcept.
tested on
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105162
Sebastian Pop changed:
What|Removed |Added
Attachment #52762|0 |1
is obsolete|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105303
Bug ID: 105303
Summary: Assertion_Policy (Pre => Ignore) executes precondition
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100052
--- Comment #11 from seurer at gcc dot gnu.org ---
These failures are still occurring. The revision change doesn't appear to have
anything to do with it given it was the "daily bump".
Regressions on 11 (power8) on update from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104050
--- Comment #2 from Iain Sandoe ---
(In reply to Martin Liška from comment #1)
> Confirmed. Interesting that one needs -save-temps. Likely started with GCC
> 11.
I compared the simple from the FE with -save-temps (FAILS) and without (OK)
the
In switch statements with dense case values, the typical result is a jump
table, which is fast. If the values are sparse, a tree of compares is
generated instead.
What if nearly all cases are dense but there are a few outliers? An example
appears in the NFS protocol parser, where you get a
At the first iteration of __from_chars_pow2_base's main loop, we need
to remember the value of the leading significant digit for sake of the
overflow check at the end of the function (for bases other than 2).
This patch manually unrolls this first iteration so as to not encumber
the entire loop
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105301
--- Comment #2 from Iain Sandoe ---
candidate patch.
https://gcc.gnu.org/pipermail/gcc-patches/2022-April/593318.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105287
--- Comment #4 from Iain Sandoe ---
candidate patch for the ICE (I am not sure if there's anything needed on the
analyser side).
https://gcc.gnu.org/pipermail/gcc-patches/2022-April/593317.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103868
Iain Sandoe changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |iains at gcc dot gnu.org
---
Whether it was intended or not, it is possible to define a coroutine promise
with multiple return_value() methods [which need not even have the same type].
We were not accounting for this possibility in the check to see whether both
return_value and return_void are specifier (which is prohibited
There are a few cases where we can generate a temporary that does not need
to be added to the coroutine frame (i.e. these are genuinely ephemeral). The
intent was that unnamed temporaries should not be 'promoted' to coroutine
frame entries. However there was a thinko and these were not actually
On Sun, Apr 17, 2022 at 6:24 PM Jason Merrill wrote:
>
> On 4/15/22 07:22, Jakub Jelinek wrote:
> > Hi!
> >
> > The CONSTRUCTOR_PLACEHOLDER_BOUNDARY bit is supposed to separate
> > PLACEHOLDER_EXPRs that should be replaced by one object or subobjects of it
> > (variable, TARGET_EXPR slot, ...)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105301
Jakub Jelinek changed:
What|Removed |Added
Target Milestone|--- |11.3
Summary|[12
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105292
Mikael Pettersson changed:
What|Removed |Added
CC||mikpelinux at gmail dot com
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105301
Iain Sandoe changed:
What|Removed |Added
Last reconfirmed||2022-04-18
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105302
--- Comment #1 from Brecht Sanders
---
P.S.: This attempt was with snapshot version 12-20220417
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105302
Bug ID: 105302
Summary: gccgo for Windows using MinGW-w64
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: go
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105301
Bug ID: 105301
Summary: [12 Regression] ICE: tree check: expected tree that
contains 'decl minimal' structure, have 'overload' in
coro_promise_type_found_p, at cp/coroutines.cc:516
55 matches
Mail list logo
