https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106061
Bug ID: 106061
Summary: [13 Regression] during GIMPLE pass: einline ICE:
verify_cgraph_node failed (edge points to wrong
declaration) with -Og
Product: gcc
On Jun 22, 2022, Jonathan Wakely wrote:
> Otherwise, if rterms defines HAVE_DIRFD this function will return a
> file descriptor and a filename (not a full path) but then
> _Dir_base::openat doesn't use ::openat and so ignores the file
> descriptor, and needs a full path.
Yuck. It does. This
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94554
--- Comment #6 from Jason Merrill ---
(In reply to Daniel Krügler from comment #3)
> The example is ill-formed because the condition of 'if constexpr' is more
> restricted than that of normal 'if': It expects "a contextually converted
> constant
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94554
Jason Merrill changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |jason at gcc dot gnu.org
Iain Sandoe wrote:
> Yes (
> # We can use an in-tree build of libintl.
> if test -f ifelse([$1],,[../gettext-runtime],[$1])/uninstalled-config.sh;
> then
>
> relative_builddir='ifelse([$1],,[${top_builddir}/..],[$1]/..)/gettext-runtime'
> .
On Jun 22, 2022, Jonathan Wakely wrote:
> P.S. there's a typo in the Subject: "symlnks" not "symlinks". I don't
> know if you intend to use that as the Git commit summary line.
Thanks, I would have, fixed. I ended up introducing the feature
abstraction macros in testsuite_fs.h, so I'll shortly
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105600
Martin Liška changed:
What|Removed |Added
Known to work||13.0
Known to fail|13.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105600
--- Comment #16 from CVS Commits ---
The master branch has been updated by Martin Liska :
https://gcc.gnu.org/g:31ce821a790caec8a2849dd67a9847e78a33d14c
commit r13-1213-g31ce821a790caec8a2849dd67a9847e78a33d14c
Author: Martin Liska
Date:
On Jun 22, 2022, Jonathan Wakely wrote:
> On Wed, 22 Jun 2022 at 08:02, Alexandre Oliva via Libstdc++
> wrote:
>>
>> Hello, Sebastian,
>>
>> On Jun 22, 2022, Sebastian Huber wrote:
>>
>> > On 22/06/2022 08:24, Alexandre Oliva via Libstdc++ wrote:
>> >> rtems6's rename() implementation
--
Hello from LinkedIn,
Is your email still active?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105964
--- Comment #4 from CVS Commits ---
The releases/gcc-12 branch has been updated by Jason Merrill
:
https://gcc.gnu.org/g:c85cea9ca165b0b771d9f913016c9dc8db46b5d7
commit r12-8507-gc85cea9ca165b0b771d9f913016c9dc8db46b5d7
Author: Jason Merrill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105908
--- Comment #3 from CVS Commits ---
The releases/gcc-12 branch has been updated by Jason Merrill
:
https://gcc.gnu.org/g:4fcf79c8ab835615aea0687195871ac43b84d156
commit r12-8506-g4fcf79c8ab835615aea0687195871ac43b84d156
Author: Jason Merrill
Hi:
This is follow-up to [1], return INVALID_REGNUM instead of gcc_assert,
also adjust some conditions guarded for reg_or_subregno.
>OK, but I think that reg_or_subregno should be improved to return
>INVALID_REGNUM when the subreg of memory is processed.
>
>Thanks,
>Uros.
[1]
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106054
--- Comment #4 from Di Zhao ---
(In reply to Andrew Pinski from comment #3)
> From https://www.spec.org/cpu2017/Docs/benchmarks/505.mcf_r.html:
> >The module spec_qsort.c does not obey strict ANSI aliasing rules. You may
> >need to add your
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105885
Jason Merrill changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105964
--- Comment #3 from CVS Commits ---
The master branch has been updated by Jason Merrill :
https://gcc.gnu.org/g:d29f61a3291a8c4cff0bd754fa3bb8e9399589bc
commit r13-1210-gd29f61a3291a8c4cff0bd754fa3bb8e9399589bc
Author: Jason Merrill
Date:
While looking at PR105964 I noticed that we were unnecessarily repeating
the deduction loop because of seeing a non-type parameter with type 'auto'.
It is indeed dependent, but not on any other deductions.
Tested x86_64-pc-linux-gnu, applying to trunk.
gcc/cp/ChangeLog:
* pt.cc
helper::c isn't dependent just because we haven't deduced its return
type yet. type_dependent_expression_p already knows how to deal with that
for bare FUNCTION_DECL, but needs to learn to look through a BASELINK.
Tested x86_64-pc-linux-gnu, applying to trunk.
PR c++/105964
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105940
Kewen Lin changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
Fix typo and commit as obvious.
Signed-off-by: Xionghu Luo
gcc/ChangeLog:
* cgraph.cc (cgraph_edge::redirect_call_stmt_to_callee): Fix
typo.
* tree-ssa-loop-ivopts.cc (struct iv_cand): Likewise.
* tree-switch-conversion.h: Likewise.
---
gcc/cgraph.cc
There is a corner case for speculative multiple targets, that if speculative
edges are streamed to different ltrans units, and then edges are expanded
in one ltrans unit but the speculative property is not cleared by
resolve_speculation in other ltrans unit finally cause ICE. This patch
fixes
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105254
--- Comment #7 from CVS Commits ---
The releases/gcc-12 branch has been updated by Kewen Lin :
https://gcc.gnu.org/g:bb1a6d92989a50df13b1a21085c86625089c9e53
commit r12-8505-gbb1a6d92989a50df13b1a21085c86625089c9e53
Author: Richard Sandiford
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105940
--- Comment #11 from CVS Commits ---
The releases/gcc-12 branch has been updated by Kewen Lin :
https://gcc.gnu.org/g:bb1a6d92989a50df13b1a21085c86625089c9e53
commit r12-8505-gbb1a6d92989a50df13b1a21085c86625089c9e53
Author: Richard Sandiford
Hi,
Gentle ping https://gcc.gnu.org/pipermail/gcc-patches/2022-June/596212.html
BR,
Kewen
on 2022/6/6 14:20, Kewen.Lin via Gcc-patches wrote:
> Hi,
>
> PR105459 exposes one issue in inline_call handling that when it
> decides to copy FP flags from callee to caller and rebuild the
>
Hi,
Gentle ping https://gcc.gnu.org/pipermail/gcc-patches/2022-May/595209.html
BR,
Kewen
>> Hi,
>>
>> As PR103353 shows, we may want to continue to expand a MMA built-in
>> function like a normal function, even if we have already emitted
>> error messages about some missing required conditions.
Hi,
Gentle ping https://gcc.gnu.org/pipermail/gcc-patches/2022-May/595208.html
BR,
Kewen
>> Hi,
>>
>> As PR104482 shown, it's one regression about the handlings when
>> the argument number is more than the one of built-in function
>> prototype. The new bif support only catches the case that
Hi,
Gentle ping https://gcc.gnu.org/pipermail/gcc-patches/2022-May/594699.html
BR,
Kewen
> on 2022/5/13 13:29, Kewen.Lin via Gcc-patches wrote:
>> Hi,
>>
>> PR105485 exposes that new builtin function framework doesn't handle
>> unresolved overloaded builtin function well. With new builtin
>>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105940
--- Comment #10 from CVS Commits ---
The releases/gcc-12 branch has been updated by Kewen Lin :
https://gcc.gnu.org/g:b3200ac82fd5aed39293a54e0e83258bb6caa600
commit r12-8504-gb3200ac82fd5aed39293a54e0e83258bb6caa600
Author: Kewen Lin
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106060
Bug ID: 106060
Summary: Inefficient constant broadcast on x86_64
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
<>
On Jun 22, 2022, Jonathan Wakely wrote:
> It looks like it would be possible for this to livelock.
True
> The current
> implementation will fail with an error in that case, rather than
> getting stuck forever in a loop.
In the equivalent livelock scenario, newly-added dir entries are added
to
On Jun 22, 2022, Sebastian Huber wrote:
> The clock_nanosleep() uses the coarse resolution which may give a time
> before now().
Uhh, sorry, hit send too early.
I also meant to ask whether you'd like me to file an RTEMS ticket about
this issue.
--
Alexandre Oliva, happy hacker
On Jun 22, 2022, Sebastian Huber wrote:
> The clock_nanosleep() uses the coarse resolution
Thanks for looking into this. So, is it missing a rounding-up to ensure
the sleep time is >= the requested time, or is it even more elaborate
than that?
--
Alexandre Oliva, happy hacker
On Wed, Jun 22, 2022 at 4:29 PM Alexandre Oliva wrote:
>
> On Jun 22, 2022, Iain Sandoe wrote:
>
> > It makes some sense to have the option named -nostdlib++ if a target
> > might add multiple libs (and/or make other changes) for linking C++.
>
> if it was nostdlibc++, I'd agree. lib++ is not
On Jun 22, 2022, Iain Sandoe wrote:
> It makes some sense to have the option named -nostdlib++ if a target
> might add multiple libs (and/or make other changes) for linking C++.
if it was nostdlibc++, I'd agree. lib++ is not something that brings
C++ to (my) mind.
> (so, fo example, if
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106059
Bug ID: 106059
Summary: [13 regression] cc.dg/vect/pr79347.c fails after
r13-1171-g9f55aee9dca759
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94899
--- Comment #6 from Gabriel Ravier ---
Can confirm that this appears to be fixed.
This patch adds a new json frontend: json-replayer, which the gcc driver
can invoke on .json files saved with -fdiagnostics-format=json-file.
gcc/ChangeLog:
* json/Make-lang.in: New file.
* json/config-lang.in: New file.
* json/json-frontend.cc: New file.
*
This patch implements JSON parsing support.
It's based on the parsing parts of the patch I posted here:
https://gcc.gnu.org/legacy-ml/gcc-patches/2017-08/msg00417.html
with the parsing moved to a separate source file and header, and heavily
rewritten to capture source location information for
This work-in-progress hacks up the file_cache code in input.cc so that
it can have an optional path remapper, which can map e.g. paths in a
.sarif file to paths relative to that .sarif file, so that the
sarif-replayer can locate and display sources.
gcc/ChangeLog:
* input.cc
Doing so allows for multiline directives to contain things like
"note: " which would otherwise already have been pruned.
gcc/testsuite/ChangeLog:
* lib/prune.exp (prune_gcc_output): Move multiline-handling to
before other pruning.
Signed-off-by: David Malcolm
---
I believe these are needed by one of the rule-handling patches.
gcc/ChangeLog:
* diagnostic-format-sarif.cc (sarif_builder::sarif_builder):
Defer population of m_driver_obj until...
(sarif_builder::make_tool_object): ...here.
This patch adds classes that better integrate the JSON parser with
GCC's diagnostic subsystem (e.g. line_maps).
gcc/ChangeLog:
* json-reader.cc: New file.
* json-reader.h: New file.
Signed-off-by: David Malcolm
---
gcc/json-reader.cc | 122
libcpp requires locations to be created as if by a tokenizer, creating
them by filename, in ascending order of line/column.
This patch adds support classes that allow the creation of locations
in arbitrary orders, by deferring all location creation,
grouping things up by filename/line, and then
gcc/ChangeLog:
* diagnostic-client-data-hooks.h
(class diagnostic_client_plugin_info): Move to...
* diagnostic-client-plugin.h: ...this new file.
* diagnostic-format-sarif.cc: Include "diagnostic-client-plugin.h".
(class sarif_tool_component): New class.
We currently have a couple of formats into which our diagnostics can
be serialized: (a) gcc's own json format and (b) SARIF, via:
-fdiagnostics-format=json-stderr (and -fdiagnostics-format=json)
-fdiagnostics-format=json-file
-fdiagnostics-format=sarif-stderr
gcc/ChangeLog:
* common.opt (fdiagnostics-show-rules): New option.
* diagnostic-format-json.cc (diagnostic_output_format_init_json):
Fix up context->show_rules.
* diagnostic-format-sarif.cc
(diagnostic_output_format_init_sarif): Likewise.
*
Obviously this isn't quite ready for trunk yet.
libcpp/ChangeLog:
* include/line-map.h (rich_location::maybe_add_fixit): Make
public.
* line-map.cc (linemap_add): Hack away assertion about LC_RENAME
for now.
Signed-off-by: David Malcolm
---
gcc/ChangeLog:
* diagnostic-core.h (emit_diagnostic): New overload.
(emit_diagnostic_valist): New overload.
* diagnostic.cc (emit_diagnostic): New overload.
(emit_diagnostic_valist): New overload.
Signed-off-by: David Malcolm
---
gcc/diagnostic-core.h | 7
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105964
Jason Merrill changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105908
--- Comment #2 from CVS Commits ---
The master branch has been updated by Jason Merrill :
https://gcc.gnu.org/g:349a39f061407ce2339d2ba25da97005f2030c88
commit r13-1207-g349a39f061407ce2339d2ba25da97005f2030c88
Author: Jason Merrill
Date:
In r12-1273 for PR91706, I removed the code in get_class_binding that
stripped BASELINK. This testcase demonstrates that we still need to strip
it in outer_binding before putting the overload set in IDENTIFIER_BINDING,
for compatibility with bindings added directly for declarations.
Tested
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105751
Andrew Pinski changed:
What|Removed |Added
CC||pinskia at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105773
Andrew Pinski changed:
What|Removed |Added
Severity|minor |enhancement
Hello, Eric,
On Jun 21, 2022, Eric Gallager wrote:
> https://gcc.gnu.org/pipermail/gcc-patches/2022-June/596654.html
> (cc-ing the build machinery maintainers listed in MAINTAINERS this time)
Thanks
> On Tue, Jun 14, 2022 at 3:51 PM Eric Gallager wrote:
>> So, in investigating PR
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106053
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |13.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106055
Andrew Pinski changed:
What|Removed |Added
Summary|[13 Regression] ICE in |[13 Regression] ICE in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106047
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105749
Andrew Pinski changed:
What|Removed |Added
Known to fail||10.3.0
--- Comment #3 from Andrew
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105749
--- Comment #2 from Andrew Pinski ---
: In function 'void t(const std::string&)':
:13:51: warning: '*(int*)((char*) +
offsetof(std::optional,std::optional::.std::_Optional_base::))' may be used uninitialized [-Wmaybe-uninitialized]
13 |
Hi Bruno,
+1 on the C reasons for removing intl.
(however, once we have a rough working patch, it would still need buy-in from
GDB + binutils)
> On 21 Jun 2022, at 03:05, Bruno Haible wrote:
>> So, indeed, part of this is quite straight forward - we can amend the
>> Makefile.def
>> to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105749
--- Comment #1 from Andrew Pinski ---
>Interesting that commenting unrelated parts or changing them slightly makes
warning go away.
Most likely inlining changes with those being there vs not being there.
On Fri, May 27, 2022 at 11:52 PM m wrote:
>
> Hello!
>
> I maintain a fork of GCC which adds support for my custom CPU ISA,
> MRISC32 (the machine description can be found here:
> https://github.com/mrisc32/gcc-mrisc32/tree/mbitsnbites/mrisc32/gcc/config/mrisc32
> ).
>
> I recently discovered
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106049
anlauf at gcc dot gnu.org changed:
What|Removed |Added
CC||anlauf at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106054
--- Comment #3 from Andrew Pinski ---
>From https://www.spec.org/cpu2017/Docs/benchmarks/505.mcf_r.html:
>The module spec_qsort.c does not obey strict ANSI aliasing rules. You may need
>to add your compiler's flag that informs it not to assume
> On 22 Jun 2022, at 01:36, Alexandre Oliva via Gcc-patches
> wrote:
>
> On Jun 21, 2022, Fangrui Song wrote:
>
>> Is this similar to clang -nostdlib++ ?
>> When libstdc++ is selected, clang -nostdlib++ removes -lstdc++.
>
> Sounds like they're the same indeed, but the clang option you
-as --disable-libstdcxx-pch
--prefix=/repo/gcc-trunk//binary-trunk-r13-1203-20220622112715-g038b077689b-checking-yes-rtl-df-extra-powerpc64le
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 13.0.0 20220622 (experimental) (GCC)
On Linux/x86_64,
038b077689bb5310386b04d40a2cea234f01e6aa is the first bad commit
commit 038b077689bb5310386b04d40a2cea234f01e6aa
Author: Richard Sandiford
Date: Wed Jun 22 11:27:15 2022 +0100
data-ref: Improve non-loop disambiguation [PR106019]
caused
FAIL: gcc.dg/tree-ssa/slsr-39.c
On Wed, 2022-06-22 at 16:57 +0200, Tim Lange wrote:
> The checker reaches region-model.cc#3083 in my patch with the
> impl_region_model_context
> on the 'after' node of create_buffer() but then discards the warning
> inside
> impl_region_model_context::warn because m_stmt is null. Even if m_stmt
On 6/22/2022 11:30 AM, Iain Buclaw via Gcc-patches wrote:
Hi,
Since around GCC 10, the condition `j < (INTMAX_MAX / 10)' will get
optimized into `j != 922337203685477580', which will result in an
infinite loop for certain inputs of `j'.
This patch just copies the condition already used by
Hi,
Since around GCC 10, the condition `j < (INTMAX_MAX / 10)' will get
optimized into `j != 922337203685477580', which will result in an
infinite loop for certain inputs of `j'.
This patch just copies the condition already used by the -DTILEPRO
generator code, which doesn't fall into the same
On Wed, Jun 22, 2022 at 4:39 AM Richard Biener
wrote:
>
> On Tue, Jun 21, 2022 at 11:03 PM H.J. Lu via Gcc-patches
> wrote:
> >
> > When memchr is applied on a constant string of no more than the bytes of
> > a word, inline memchr by checking each byte in the constant string.
> >
> > int f (int
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106057
--- Comment #1 from Jan Hubicka ---
C only testcase (also misoptimized in clang)
#include
int b;
jmp_buf buf;
__attribute__((noinline))
int maybethrow()
{
if (!b)
longjmp (buf,1);
return 2;
}
void
test(int
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106057
Bug ID: 106057
Summary: Missed stmt_can_throw_external check in
stmt_kills_ref_p
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Hi,
This patch merges the D front-end with upstream dmd 6203135dc, and the D
run-time library with upstream druntime e150cca1, and phobos a4a18d21c.
D front-end changes:
- Input parameters can now be applied on extern(C++) functions to
bind to `const &' when the `-fpreview=in' flag is
The only reason I chose to use DECL_UID on this hash table was to make
it stable against ASLR and perturbations due to other allocations.
It's not required for correctness, as the comment mentions the
equality fn uses pointer identity.
nathan
--
Nathan SidwellFrom
The checker reaches region-model.cc#3083 in my patch with the
impl_region_model_context
on the 'after' node of create_buffer() but then discards the warning inside
impl_region_model_context::warn because m_stmt is null. Even if m_stmt were
not be NULL at the 'after' node, my warning would be
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104642
Jason Merrill changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105660
--- Comment #4 from Romain Dolbeau ---
It seems the issue was an 'r' dropped from the name of 'strrchr' in the
offending commit. Fixing this resolves the bug for us. See the attached patch.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105660
Romain Dolbeau changed:
What|Removed |Added
CC||romain at dolbeau dot org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104642
--- Comment #6 from CVS Commits ---
The master branch has been updated by Jason Merrill :
https://gcc.gnu.org/g:d68d366425369649cb4e25a07752e25a4fff52cf
commit r13-1204-gd68d366425369649cb4e25a07752e25a4fff52cf
Author: Jason Merrill
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106056
Bug ID: 106056
Summary: Missing call to targetm.asm_out.final_postscan_insn
after processing an asm_input
Product: gcc
Version: 10.3.1
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93371
Caleb Zulawski changed:
What|Removed |Added
CC||caleb.zulawski at gmail dot com
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106054
--- Comment #2 from Andrew Pinski ---
It is the access via different pointer types. That is the issue.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106054
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
Hello,
I added the ! default_packed directive, and now the test is properly
skipped on the targets with that property. I tested with cris-elf
target and the test behaves properly.
Best regards,
Vit Kabele
-- >8 --
Subject: [PATCH v2] c: Extend the -Wpadded message with actual padding size
When
On Tue, Jun 21, 2022 at 11:03 PM H.J. Lu via Gcc-patches
wrote:
>
> When memchr is applied on a constant string of no more than the bytes of
> a word, inline memchr by checking each byte in the constant string.
>
> int f (int a)
> {
>return __builtin_memchr ("eE", a, 2) != 0;
> }
>
> is
This patch addresses PR target/105930 which is an ia32 stack frame size
regression in high-register pressure XOR-rich cryptography functions
reported by Linus Torvalds. The underlying problem is once the limited
number of registers on the x86 are exhausted, the register allocator
has to decide
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106052
Jonathan Wakely changed:
What|Removed |Added
Ever confirmed|0 |1
Keywords|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106051
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
> @Honza: PING
>
> On 5/20/22 09:46, Martin Liška wrote:
> > On 5/19/22 17:02, Jan Hubicka wrote:
> >>> Similarly to cgraph_nodes, it may happen that body_removed is set
> >>> during merging of symbols.
> >>>
> >>> PR ipa/105600
> >>>
> >>> Patch can bootstrap on x86_64-linux-gnu and survives
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106051
Jonathan Wakely changed:
What|Removed |Added
Keywords||rejects-valid
CC|
On Wed, 22 Jun 2022 at 07:35, Alexandre Oliva via Libstdc++
wrote:
>
>
> The last_write_time functions are defined in ways that are useful, or
> that fail immediately, depending on various macros. When they fail
> immediately, the filesystem last_write_time.cc tests fail noisily, but
> the fail
On Wed, 22 Jun 2022 at 10:25, Jonathan Wakely wrote:
>
> On Wed, 22 Jun 2022 at 07:14, Alexandre Oliva via Libstdc++
> wrote:
> >
> >
> > Several filesystem tests expect to be able to create symlinks even
> > when !defined (_GLIBCXX_HAVE_SYMLINK), and fail predictably, reducing
> > the amount of
On Wed, 22 Jun 2022 at 08:02, Alexandre Oliva via Libstdc++
wrote:
>
> Hello, Sebastian,
>
> On Jun 22, 2022, Sebastian Huber wrote:
>
> > On 22/06/2022 08:24, Alexandre Oliva via Libstdc++ wrote:
> >> rtems6's rename() implementation errors with EEXIST when the rename-to
> >> filename exists,
On Wed, 22 Jun 2022 at 07:43, Alexandre Oliva via Libstdc++
wrote:
>
>
> rtems6.0 has fdopendir, and fcntl.h defines AT_FDCWD and declares
> openat, but there's no openat in libc. Adjust dir-common.h to not
> assume ::openat just because of AT_FDCWD.
>
> Regstrapped on x86_64-linux-gnu (detects
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53947
Bug 53947 depends on bug 106019, which changed state.
Bug 106019 Summary: Surprising SLP failure on trivial code
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106019
What|Removed |Added
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106019
rsandifo at gcc dot gnu.org changed:
What|Removed |Added
Resolution|--- |FIXED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106019
--- Comment #4 from CVS Commits ---
The trunk branch has been updated by Richard Sandiford :
https://gcc.gnu.org/g:038b077689bb5310386b04d40a2cea234f01e6aa
commit r13-1203-g038b077689bb5310386b04d40a2cea234f01e6aa
Author: Richard Sandiford
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106055
Bug ID: 106055
Summary: [13 Regression] ICE in replace_uses_by, at
tree-cfg.cc:1989
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Keywords: ice-on-valid-code
1 - 100 of 132 matches
Mail list logo