From: Florian Weimer <fw@deneb.enyo.de>
To: Sandra Loosemore <sandra@codesourcery.com>
Cc: Joseph Myers <joseph@codesourcery.com>,
Florian Weimer <fweimer@redhat.com>,
<libc-alpha@sourceware.org>,
Szabolcs Nagy <szabolcs.nagy@arm.com>,
<cltang@codesourcery.com>, <andrew@codesourcery.com>
Subject: Re: [review v3] slotinfo in struct dtv_slotinfo_list should be flexible array [BZ #25...
Date: Wed, 13 Nov 2019 06:47:01 +0100 [thread overview]
Message-ID: <87v9ro9vl6.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <55541dd4-7e5e-e7ec-ae17-e9904041780e@codesourcery.com> (Sandra Loosemore's message of "Tue, 12 Nov 2019 13:59:47 -0700")
* Sandra Loosemore:
> OK, having a self-contained test case is very helpful. I'll take a look
> at fixing this in GCC, although I might not get to it for a few days.
> Probably the solution is to not use GP-relative addressing for any
> object declared with a flexible array member.
Thanks for looking into this. Should I file a GCC PR?
next prev parent reply other threads:[~2019-11-13 5:47 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-03 17:11 [review] slotinfo in struct dtv_slotinfo_list should be flexible array [BZ #25 Florian Weimer (Code Review)
2019-11-06 16:12 ` Szabolcs Nagy
2019-11-06 16:21 ` Florian Weimer
2019-11-11 15:09 ` Szabolcs Nagy
2019-11-11 15:12 ` Florian Weimer
2019-11-11 21:41 ` Sergio Durigan Junior
2019-11-12 10:22 ` Szabolcs Nagy
2019-11-12 10:35 ` Florian Weimer
2019-11-09 11:44 ` [review v2] " Florian Weimer (Code Review)
2019-11-12 10:40 ` Szabolcs Nagy (Code Review)
2019-11-12 11:47 ` [review v3] " Florian Weimer (Code Review)
2019-11-12 17:29 ` Joseph Myers
2019-11-12 17:42 ` Sandra Loosemore
2019-11-12 18:04 ` Joseph Myers
2019-11-12 18:42 ` Florian Weimer
2019-11-12 20:59 ` Sandra Loosemore
2019-11-13 5:47 ` Florian Weimer [this message]
2019-11-13 16:04 ` Sandra Loosemore
2019-11-13 16:25 ` Florian Weimer
2019-11-13 16:06 ` Jeff Law
2019-11-12 22:14 ` Carlos O'Donell
2019-11-12 22:18 ` Florian Weimer
2019-11-12 22:24 ` Carlos O'Donell
2019-11-12 22:26 ` Florian Weimer
2019-11-12 22:39 ` Joseph Myers
2019-11-13 6:18 ` Florian Weimer
2019-11-13 16:05 ` Jeff Law
2019-11-12 23:12 ` Sandra Loosemore
2019-11-12 23:15 ` Joseph Myers
2019-11-12 12:53 ` Szabolcs Nagy (Code Review)
2019-11-12 13:00 ` [pushed] " Sourceware to Gerrit sync (Code Review)
2019-11-12 13:00 ` Sourceware to Gerrit sync (Code Review)
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87v9ro9vl6.fsf@mid.deneb.enyo.de \
--to=fw@deneb.enyo.de \
--cc=andrew@codesourcery.com \
--cc=cltang@codesourcery.com \
--cc=fweimer@redhat.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=sandra@codesourcery.com \
--cc=szabolcs.nagy@arm.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).