> I'm kind of torn on this one: this has been around for a while and
> dropping it would be an ABI break, but the feedback from distro folks is
> pretty consistently that multlib is broken on RISC-V. If it's really
> unusably broken then I could buy the argument that there's no binaries
> (and
On Sat, Jul 9, 2022 at 11:59 PM Jeff Law via Gcc-patches
wrote:
>
>
>
> On 7/9/2022 2:52 PM, Lewis Hyatt via Gcc-patches wrote:
> > Hello-
> >
> > PR97498 (https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97498) is another PR
> > related to the fact that imprecise locations for _Pragma result in
> > c
> Hi Lewis,
>
> Thanks! Good spot. I think it should be calling dg-runtest however,
> same as what libphobos.cycles/cycles.exp is doing. Could also fix the
> test name so each one is unique, just to hit two birds in one -
> something like the following would suffice (haven't had time to check).
>
On 7/15/22 22:25, Marek Polacek via Gcc-patches wrote:
Yeah, I guess so. But I've already pushed the patch.
This commit obviously breaks using libstdc++ with Clang (in -std=c++2b
mode), which doesn't implement those new builtins. Something like the
below would fix that,
diff --git a/libs
On Sat, Jul 16, 2022 at 10:08 PM Roger Sayle wrote:
>
>
> This AVX512 specific patch to sse.md is split out from an earlier patch:
> https://gcc.gnu.org/pipermail/gcc-patches/2022-June/596199.html
>
> The new splitters proposed in that patch interfere with AVX512's
> kunpckdq instruction which is
And split it after reload.
>IMO, the only case it is worth adding is a direct immediate store to
>memory, which HJ recently added.
Bootstrapped and regtested on x86_64-pc-linux-gnu{-m32,}.
Ok for trunk?
gcc/ChangeLog:
PR target/106038
* config/i386/mmx.md (3): Extend to AND mem,
V2 update:
Handle VMAT_ELEMENTWISE, VMAT_CONTIGUOUS_PERMUTE, VMAT_STRIDED_SLP,
VMAT_CONTIGUOUS_REVERSE, VMAT_CONTIGUOUS_DOWN for complex type.
I've run SPECspeed@2017 627.cam4_s, there's some vectorization cases,
but no big performance impact(since this patch only handle load/store).
Any co
On Sat, Jul 16, 2022 at 2:06 PM Roger Sayle wrote:
>
>
> This patch fixes (what I believe is) a latent bug in i386.md's
> x86_64_const_vector_operand define_predicate. According to the
> documentation, when a predicate is called with rtx operand OP and
> machine_mode operand MODE, we can't should
On Sat, Jul 16, 2022 at 9:10 PM Roger Sayle wrote:
>
>
> This patch resolves PR target/106231 by providing insns that recognize
> (zero_extend:DI (ctz:SI ...)) and (sign_extend:DI (ctz:SI ...)). The
> result of ctz:SI is always between 0 and 32 (or undefined), so
> sign_extension is the same as z
On Fri, Jul 15, 2022 at 3:49 PM Prathamesh Kulkarni
wrote:
>
> On Thu, 14 Jul 2022 at 17:22, Richard Sandiford
> wrote:
> >
> > Richard Biener writes:
> > > On Thu, Jul 14, 2022 at 9:55 AM Prathamesh Kulkarni
> > > wrote:
> > >>
> > >> On Wed, 13 Jul 2022 at 12:22, Richard Biener
> > >> wrote
On Mon, Jul 18, 2022 at 3:59 AM liuhongt wrote:
>
> And split it after reload.
>
> >IMO, the only case it is worth adding is a direct immediate store to
> >memory, which HJ recently added.
>
> Bootstrapped and regtested on x86_64-pc-linux-gnu{-m32,}.
> Ok for trunk?
>
> gcc/ChangeLog:
>
>
On Sat, Jul 16, 2022 at 2:54 PM Roger Sayle wrote:
>
>
> This middle-end patch resolves PR c/106264 which is a spurious warning
> regression caused by the tree-level expansion of modf, frexp and remquo
> producing "expression has no-effect" when the built-in function's result
> is ignored. When t
12 matches
Mail list logo
