Hi Suwa-san,
On Fri, Oct 14, 2022 at 4:19 AM Takayuki 'January June' Suwa
wrote:
> This patch provides the first step in the transition from Reload to LRA
> in Xtensa.
>
> gcc/ChangeLog:
>
> * config/xtensa/xtensa-proto.h (xtensa_split1_is_finished_p):
> New prototype.
> *
Spotted while looking at a regression on the H8/300. We used MAC_REG
rather than MAC_REGS when referring to a register class. This caused
code quality regressions while looking into Paul K's suggestion for
fixing the auto-increment issue on the H8.
Pushed to the trunk,
Jeff
commit 6c3d
On 10/14/22 13:00, Patrick Palka wrote:
IIUC we currently avoid streaming the RESULT_DECL and PARM_DECLs
of a constexpr_fundef entry under the assumption that they're just
copies of the DECL_RESULT and DECL_ARGUMENTS of the FUNCTION_DECL.
Thus we can just make new copies of DECL_RESULT and DECL_A
On Sat, 15 Oct 2022 at 14:30, Jonathan Wakely wrote:
>
> On Sat, 15 Oct 2022 at 11:52, Thomas Schwinge wrote:
> >
> > Hi!
> >
> > On 2022-10-14T15:36:02+0100, Jonathan Wakely via Gcc-patches
> > wrote:
> > > Tested powerpc64le-linux. Pushed to trunk.
> > >
> > > -- >8 --
> > >
> > > Replace two
This has been approved for C++23.
I've just realised that the commit msg doesn't match the actual patch. I
had a consteval lambda in an earlier version, but I changed it to do:
+#if __cpp_lib_constexpr_charconv
+ if (std::__is_constant_evaluated())
+ return __table<_DecOnly>.__d
This issue is Tentatively Ready, and the resolution seems obviously
correct so we can do it now.
Tested powerpc64le-linux. Pushed to trunk.
-- >8 --
The _Std_pair concept uses in handles const
qualified pairs, but not volatile qualified. That's because it just uses
__is_pair which is specialize
Hi,
recently I used some arduino uno for a project and realized some areas
which do not output optimal asm code. Especially around shifts and function
calls.
With this as motivation and hacktoberfest I started patching things.
Since patch files do not provide a good overview and I hope for a
"hack
On Sat, 15 Oct 2022 at 11:52, Thomas Schwinge wrote:
>
> Hi!
>
> On 2022-10-14T15:36:02+0100, Jonathan Wakely via Gcc-patches
> wrote:
> > Tested powerpc64le-linux. Pushed to trunk.
> >
> > -- >8 --
> >
> > Replace two uses of print_raw where it's clearer to just use fprintf
> > directly. Then t
On 12.10.22 19:57, Jeff Law wrote:
On 10/4/22 11:06, Alexander Binzberger via Gcc-patches wrote:
Hi,
recently I used some arduino uno for a project and realized some areas
which do not output optimal asm code. Especially around shifts and
function
calls.
With this as motivation and hacktoberf
Hi!
On 2022-10-14T15:36:02+0100, Jonathan Wakely via Gcc-patches
wrote:
> Tested powerpc64le-linux. Pushed to trunk.
>
> -- >8 --
>
> Replace two uses of print_raw where it's clearer to just use fprintf
> directly. Then the only remaining use of print_raw is as the print_func
> argument of prett
On Sat, Oct 15, 2022 at 10:07:46AM +0200, Martin Uecker wrote:
> But why? Do we really want to encourage people to
> write such code?
Of course these ++ cases inside of expressions are just obfuscation.
But the point is to support using predicates that can be inlined and
simplified into something
Am Freitag, den 14.10.2022, 23:20 +0200 schrieb Jakub Jelinek:
> On Fri, Oct 14, 2022 at 10:43:16PM +0200, Martin Uecker wrote:
> > Am Montag, den 10.10.2022, 10:54 +0200 schrieb Jakub Jelinek:
> > > Hi!
> > >
> > > My earlier patches gimplify the simplest non-side-effects assumptions
> > > into i
12 matches
Mail list logo
