On Wed, Jul 5, 2023 at 9:51 AM Thomas Schwinge wrote:
>
> Hi!
>
> On 2022-10-18T18:14:54-0400, Lewis Hyatt via Gcc-patches
> wrote:
> > [...] add a new
> > GTY option "string_length" so that gt_pch_note_object can be informed the
> > actual length it ought to use, [...]
>
> > --- a/gcc/doc/gty.t
Hi!
On 2023-07-04T15:56:23-0400, Lewis Hyatt via Gcc-patches
wrote:
> On Tue, Jul 4, 2023 at 11:50 AM Thomas Schwinge
> wrote:
>> I came across this one here on my way working through another (somewhat
>> related) GTY issue. I generally do understand the issue here, but do
>> have a question
Hi!
On 2022-10-18T18:14:54-0400, Lewis Hyatt via Gcc-patches
wrote:
> [...] add a new
> GTY option "string_length" so that gt_pch_note_object can be informed the
> actual length it ought to use, [...]
> --- a/gcc/doc/gty.texi
> +++ b/gcc/doc/gty.texi
> @@ -196,7 +196,26 @@ static GTY((length("r
On Tue, Jul 4, 2023 at 11:50 AM Thomas Schwinge wrote:
>
> Hi!
>
> I came across this one here on my way working through another (somewhat
> related) GTY issue. I generally do understand the issue here, but do
> have a question about 'unsigned int len' field in
> 'libcpp/include/symtab.h:struct h
Hi!
I came across this one here on my way working through another (somewhat
related) GTY issue. I generally do understand the issue here, but do
have a question about 'unsigned int len' field in
'libcpp/include/symtab.h:struct ht_identifier':
On 2022-10-18T18:14:54-0400, Lewis Hyatt via Gcc-patc
On Wed, Oct 19, 2022 at 8:23 AM Jakub Jelinek wrote:
>
> On Wed, Oct 19, 2022 at 01:17:02PM +0100, Richard Sandiford wrote:
> > Jakub Jelinek writes:
> > > On Wed, Oct 19, 2022 at 12:54:11PM +0100, Richard Sandiford via
> > > Gcc-patches wrote:
> > >> Lewis Hyatt via Gcc-patches writes:
> > >>
On Wed, Oct 19, 2022 at 01:17:02PM +0100, Richard Sandiford wrote:
> Jakub Jelinek writes:
> > On Wed, Oct 19, 2022 at 12:54:11PM +0100, Richard Sandiford via Gcc-patches
> > wrote:
> >> Lewis Hyatt via Gcc-patches writes:
> >> > When a GTY'ed struct is streamed to PCH, any plain char* pointers
Jakub Jelinek writes:
> On Wed, Oct 19, 2022 at 12:54:11PM +0100, Richard Sandiford via Gcc-patches
> wrote:
>> Lewis Hyatt via Gcc-patches writes:
>> > When a GTY'ed struct is streamed to PCH, any plain char* pointers it
>> > contains
>> > (whether they live in GC-controlled memory or not) wil
On Wed, Oct 19, 2022 at 12:54:11PM +0100, Richard Sandiford via Gcc-patches
wrote:
> Lewis Hyatt via Gcc-patches writes:
> > When a GTY'ed struct is streamed to PCH, any plain char* pointers it
> > contains
> > (whether they live in GC-controlled memory or not) will be marked for PCH
> > output
Lewis Hyatt via Gcc-patches writes:
> When a GTY'ed struct is streamed to PCH, any plain char* pointers it contains
> (whether they live in GC-controlled memory or not) will be marked for PCH
> output by the routine gt_pch_note_object in ggc-common.cc. This routine
> special-cases plain char* stri
When a GTY'ed struct is streamed to PCH, any plain char* pointers it contains
(whether they live in GC-controlled memory or not) will be marked for PCH
output by the routine gt_pch_note_object in ggc-common.cc. This routine
special-cases plain char* strings, and in particular it uses strlen() to ge
11 matches
Mail list logo