On 5/3/23 08:33, Palmer Dabbelt wrote:
On Wed, 03 May 2023 08:13:23 PDT (-0700), jeffreya...@gmail.com wrote:
On 5/3/23 08:14, Palmer Dabbelt wrote:
On Wed, 03 May 2023 02:49:41 PDT (-0700), richard.guent...@gmail.com
wrote:
On Wed, May 3, 2023 at 8:33 AM Jeff Law via Gcc-patches
wrote:
On Wed, 03 May 2023 08:13:23 PDT (-0700), jeffreya...@gmail.com wrote:
On 5/3/23 08:14, Palmer Dabbelt wrote:
On Wed, 03 May 2023 02:49:41 PDT (-0700), richard.guent...@gmail.com wrote:
On Wed, May 3, 2023 at 8:33 AM Jeff Law via Gcc-patches
wrote:
On 5/2/23 14:34, Patrick O'Neill wrote:
On 5/3/23 08:14, Palmer Dabbelt wrote:
On Wed, 03 May 2023 02:49:41 PDT (-0700), richard.guent...@gmail.com wrote:
On Wed, May 3, 2023 at 8:33 AM Jeff Law via Gcc-patches
wrote:
On 5/2/23 14:34, Patrick O'Neill wrote:
> Is this OK for a backport to GCC-13 as well?
Let me sync with Richi
On Wed, 03 May 2023 02:49:41 PDT (-0700), richard.guent...@gmail.com wrote:
On Wed, May 3, 2023 at 8:33 AM Jeff Law via Gcc-patches
wrote:
On 5/2/23 14:34, Patrick O'Neill wrote:
> Is this OK for a backport to GCC-13 as well?
Let me sync with Richi & Jakub. They're the release managers and
On Wed, May 3, 2023 at 8:33 AM Jeff Law via Gcc-patches
wrote:
>
>
>
> On 5/2/23 14:34, Patrick O'Neill wrote:
> > Is this OK for a backport to GCC-13 as well?
> Let me sync with Richi & Jakub. They're the release managers and this
> doesn't fall under the usual rules for things that can be backp
On 5/2/23 14:34, Patrick O'Neill wrote:
Is this OK for a backport to GCC-13 as well?
Let me sync with Richi & Jakub. They're the release managers and this
doesn't fall under the usual rules for things that can be backported.
jeff
Is this OK for a backport to GCC-13 as well?
(with the whitespace fixes/changelog revision squashed into it)
Patrick
On 4/26/23 10:01, Patrick O'Neill wrote:
Committed - I had to reformat the changelog so it would push and resolve a
trivial merge conflict in riscv.opt.
---
RISC-V has no supp
