On Mon, 28 Nov 2022 at 06:07, François Dumont via Libstdc++ <
libstd...@gcc.gnu.org> wrote:
> This patch is fixing those tests:
>
> 20_util/to_chars/float128_c++23.cc
> std/format/formatter/requirements.cc
> std/format/functions/format.cc
> std/format/functions/format_to_n.cc
>
On Mon, 28 Nov 2022 at 10:06, Jonathan Wakely wrote:
>
>
> On Mon, 28 Nov 2022 at 06:02, François Dumont via Libstdc++ <
> libstd...@gcc.gnu.org> wrote:
>
>> libstdc++: [_GLIBCXX_INLINE_VERSION] Adapt dg error messages
>>
>> libstdc++-v3/ChangeLog
>>
>> *
On Mon, 28 Nov 2022 at 06:02, François Dumont via Libstdc++ <
libstd...@gcc.gnu.org> wrote:
> libstdc++: [_GLIBCXX_INLINE_VERSION] Adapt dg error messages
>
> libstdc++-v3/ChangeLog
>
> * testsuite/20_util/bind/ref_neg.cc: Adapt dg-prune-output
> message.
> *
PING^4
On 4/7/22 16:00, Martin Liška wrote:
PING^3
On 3/24/22 11:22, Martin Liška wrote:
PING^2
On 3/4/22 14:47, Martin Liška wrote:
PING^1
On 1/26/22 12:11, Martin Liška wrote:
Hello.
Right now, switch lowering does not update basic_block::count values
so that they are uninitiliazed.
On 11/25/22 17:18, Martin Liška wrote:
On 11/21/22 11:02, Jakub Jelinek wrote:
Otherwise LGTM. Thanks and sorry for the review delay.
Yuri, do you want to commit the patch soon?
If not, I can help if you want?
Hey.
I've just installed the patch with function signature change
and
On Linux/x86_64,
a1ecc5600464f6a62faab246d522b6328badda90 is the first bad commit
commit a1ecc5600464f6a62faab246d522b6328badda90
Author: liuhongt
Date: Wed Nov 23 21:58:09 2022 +0800
Fix incorrect _mm_cvtsbh_ss.
caused
FAIL: g++.dg/other/pr39060.C -std=c++98 (internal compiler error:
On 28/11/2022 07:40, Tobias Burnus wrote:
It turned out that cprop cleverly propagated the unspec_volatile
to the preceding (pseudo)register, permitting to remove the
'set (s0) (pseudoregister)' at -O2. Unfortunately, it does
matter whether the assignment is done to 's2' (previously:
Andrea Corallo writes:
> Hi all,
>
> this is the first patch series about improving the current MVE
> implementation and testsuite for:
>
> - Complete intrinsic implementation and coverage (the list of intrinsics is
> specified by [1])
> - Verifying all instructions supposedly emitted by each
The following shows a missed update of dominators when unswitching
removes unreachable edges from switch stmts it unswitches. Fixed
by wiping dominator info in that case.
Bootstrapped and tested on x86_64-unknown-linux-gnu, pushed.
PR tree-optimization/107876
*
On Mon, Nov 28, 2022 at 9:46 AM Jakub Jelinek wrote:
>
> Hi!
>
> The following testcase fails since my changes to make also
> opts_set saved/restored upon function target/optimization changes
> (before it has been acting as "has this option be ever explicit
> anywhere?").
>
> The problem is that
Hi!
The following testcase fails since my changes to make also
opts_set saved/restored upon function target/optimization changes
(before it has been acting as "has this option be ever explicit
anywhere?").
The problem is that for ix86_abi we depend on the opts_set
value for it in
On Mon, Nov 28, 2022 at 6:33 AM HAO CHEN GUI via Gcc-patches
wrote:
>
> Hi,
>Gentle ping this:
> https://gcc.gnu.org/pipermail/gcc-patches/2022-November/607083.html
> Thanks
> Gui Haochen
>
> 在 2022/11/23 10:54, HAO CHEN GUI 写道:
> > Hi,
> > I want to enable "have_cbranchcc4" on rs6000. But
On Sat, Nov 26, 2022 at 9:41 AM Zopolis0 wrote:
>
> > What happens if you remove end_params_node from the Java front-end and
> > replace it with void_list_node?
>
> Sadly, nothing.
But that looks like the correct thing to do.
On Sat, Nov 26, 2022 at 1:19 AM Zopolis0 wrote:
>
> I was reverting a076632e274abe344ca7648b7c7f299273d4cbe0 as it removed code
> for Java, but I may have misunderstood the change and made the incorrect
> edits.
The change is fixing a bug (setting TREE_ADDRESSABLE from a CTOR in
debug stmts)
101 - 114 of 114 matches
Mail list logo
