From: Richard Biener <richard.guenther@gmail.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Jeff Law <jeffreyalaw@gmail.com>,
Jason Merrill <jason@redhat.com>,
gcc-patches@gcc.gnu.org
Subject: Re: Patch ping (Re: [PATCH] libgcc: Decrease size of _Unwind_FrameState and even more size of cleared area in uw_frame_state_for)
Date: Thu, 6 Oct 2022 10:08:18 +0200 [thread overview]
Message-ID: <CAFiYyc3g7YeOffYOso40Xscsugum3U_xAPn288qS3nvaCGxW+A@mail.gmail.com> (raw)
In-Reply-To: <Yz1daac/57+3JBi6@tucnak>
On Wed, Oct 5, 2022 at 12:34 PM Jakub Jelinek via Gcc-patches
<gcc-patches@gcc.gnu.org> wrote:
>
> Hi!
>
> I'd like to ping this patch.
The patch is OK.
Richard.
> Thanks.
>
> > 2022-09-19 Jakub Jelinek <jakub@redhat.com>
> >
> > * unwind-dw2.h (REG_UNSAVED, REG_SAVED_OFFSET, REG_SAVED_REG,
> > REG_SAVED_EXP, REG_SAVED_VAL_OFFSET, REG_SAVED_VAL_EXP,
> > REG_UNDEFINED): New anonymous enum, moved from inside of
> > struct frame_state_reg_info.
> > (struct frame_state_reg_info): Remove reg[].how element and the
> > anonymous enum there. Add how element.
> > * unwind-dw2.c: Include stddef.h.
> > (uw_frame_state_for): Don't clear first
> > offsetof (_Unwind_FrameState, regs.how[0]) bytes of *fs.
> > (execute_cfa_program, __frame_state_for, uw_update_context_1,
> > uw_update_context): Use fs->regs.how[X] instead of fs->regs.reg[X].how
> > or fs.regs.how[X] instead of fs.regs.reg[X].how.
> > * config/sh/linux-unwind.h (sh_fallback_frame_state): Likewise.
> > * config/bfin/linux-unwind.h (bfin_fallback_frame_state): Likewise.
> > * config/pa/linux-unwind.h (pa32_fallback_frame_state): Likewise.
> > * config/pa/hpux-unwind.h (UPDATE_FS_FOR_SAR, UPDATE_FS_FOR_GR,
> > UPDATE_FS_FOR_FR, UPDATE_FS_FOR_PC, pa_fallback_frame_state):
> > Likewise.
> > * config/alpha/vms-unwind.h (alpha_vms_fallback_frame_state):
> > Likewise.
> > * config/alpha/linux-unwind.h (alpha_fallback_frame_state): Likewise.
> > * config/arc/linux-unwind.h (arc_fallback_frame_state,
> > arc_frob_update_context): Likewise.
> > * config/riscv/linux-unwind.h (riscv_fallback_frame_state): Likewise.
> > * config/nios2/linux-unwind.h (NIOS2_REG): Likewise.
> > * config/nds32/linux-unwind.h (NDS32_PUT_FS_REG): Likewise.
> > * config/s390/tpf-unwind.h (s390_fallback_frame_state): Likewise.
> > * config/s390/linux-unwind.h (s390_fallback_frame_state): Likewise.
> > * config/sparc/sol2-unwind.h (sparc64_frob_update_context,
> > MD_FALLBACK_FRAME_STATE_FOR): Likewise.
> > * config/sparc/linux-unwind.h (sparc64_fallback_frame_state,
> > sparc64_frob_update_context, sparc_fallback_frame_state): Likewise.
> > * config/i386/sol2-unwind.h (x86_64_fallback_frame_state,
> > x86_fallback_frame_state): Likewise.
> > * config/i386/w32-unwind.h (i386_w32_fallback_frame_state): Likewise.
> > * config/i386/linux-unwind.h (x86_64_fallback_frame_state,
> > x86_fallback_frame_state): Likewise.
> > * config/i386/freebsd-unwind.h (x86_64_freebsd_fallback_frame_state):
> > Likewise.
> > * config/i386/dragonfly-unwind.h
> > (x86_64_dragonfly_fallback_frame_state): Likewise.
> > * config/i386/gnu-unwind.h (x86_gnu_fallback_frame_state): Likewise.
> > * config/csky/linux-unwind.h (csky_fallback_frame_state): Likewise.
> > * config/aarch64/linux-unwind.h (aarch64_fallback_frame_state):
> > Likewise.
> > * config/aarch64/freebsd-unwind.h
> > (aarch64_freebsd_fallback_frame_state): Likewise.
> > * config/aarch64/aarch64-unwind.h (aarch64_frob_update_context):
> > Likewise.
> > * config/or1k/linux-unwind.h (or1k_fallback_frame_state): Likewise.
> > * config/mips/linux-unwind.h (mips_fallback_frame_state): Likewise.
> > * config/loongarch/linux-unwind.h (loongarch_fallback_frame_state):
> > Likewise.
> > * config/m68k/linux-unwind.h (m68k_fallback_frame_state): Likewise.
> > * config/xtensa/linux-unwind.h (xtensa_fallback_frame_state):
> > Likewise.
> > * config/rs6000/darwin-fallback.c (set_offset): Likewise.
> > * config/rs6000/aix-unwind.h (MD_FROB_UPDATE_CONTEXT): Likewise.
> > * config/rs6000/linux-unwind.h (ppc_fallback_frame_state): Likewise.
> > * config/rs6000/freebsd-unwind.h (frob_update_context): Likewise.
>
> Jakub
>
next prev parent reply other threads:[~2022-10-06 8:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-19 7:58 [PATCH] libgcc: Decrease size of _Unwind_FrameState and even more size of cleared area in uw_frame_state_for Jakub Jelinek
2022-09-19 8:57 ` Richard Biener
2022-09-19 9:16 ` Jakub Jelinek
2022-09-19 9:25 ` Florian Weimer
2022-09-19 9:33 ` Jakub Jelinek
2022-09-19 13:46 ` Florian Weimer
2022-10-05 10:33 ` Patch ping (Re: [PATCH] libgcc: Decrease size of _Unwind_FrameState and even more size of cleared area in uw_frame_state_for) Jakub Jelinek
2022-10-06 8:08 ` Richard Biener [this message]
2022-10-06 22:05 ` Joseph Myers
2022-10-06 22:19 ` [committed] libgcc, arc: Fix build Jakub Jelinek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAFiYyc3g7YeOffYOso40Xscsugum3U_xAPn288qS3nvaCGxW+A@mail.gmail.com \
--to=richard.guenther@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=jason@redhat.com \
--cc=jeffreyalaw@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).