Thank you for your insight. I will investigate further and see if I can
find out what is going on.
J'
On Thu, Sep 13, 2018 at 01:33:34PM -0400, Jason Merrill wrote:
Well, that's curious, given that GCC doesn't have that address type either.
Ah, looking closer, I see that we aren
On Thu, Sep 13, 2018 at 1:35 AM, John Darrington
wrote:
> On Mon, Sep 10, 2018 at 04:40:58PM +0100, Jason Merrill wrote:
> On Mon, Sep 10, 2018 at 3:42 PM, John Darrington
> wrote:
> > On Mon, Sep 10, 2018 at 03:36:26PM +0100, Jason Merrill wrote:
> > On Mon, Aug 27, 2018
On Mon, Sep 10, 2018 at 04:40:58PM +0100, Jason Merrill wrote:
On Mon, Sep 10, 2018 at 3:42 PM, John Darrington
wrote:
> On Mon, Sep 10, 2018 at 03:36:26PM +0100, Jason Merrill wrote:
> On Mon, Aug 27, 2018 at 8:20 PM, John Darrington
> wrote:
> >
On Mon, Sep 10, 2018 at 3:42 PM, John Darrington
wrote:
> On Mon, Sep 10, 2018 at 03:36:26PM +0100, Jason Merrill wrote:
> On Mon, Aug 27, 2018 at 8:20 PM, John Darrington
> wrote:
> > * include/dwarf2.h (enum dwarf_unit_type) [DE_EH_PE_udata3]:
> New member.
>
>
> Wh
On Mon, Sep 10, 2018 at 03:36:26PM +0100, Jason Merrill wrote:
On Mon, Aug 27, 2018 at 8:20 PM, John Darrington
wrote:
> * include/dwarf2.h (enum dwarf_unit_type) [DE_EH_PE_udata3]: New
member.
What's the rationale? Do you have a separate patch that uses t
On Mon, Aug 27, 2018 at 8:20 PM, John Darrington
wrote:
> * include/dwarf2.h (enum dwarf_unit_type) [DE_EH_PE_udata3]: New
> member.
This is a new macro, not a member of dwarf_unit_type.
What's the rationale? Do you have a separate patch that uses this new macro?
Jason
Ping!
Does anyone have any objections or comments?
J'
* include/dwarf2.h (enum dwarf_unit_type) [DE_EH_PE_udata3]: New member.
---
include/dwarf2.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/dwarf2.h b/include/dwarf2.h
index cf0039a92a..0fe88a3a7e 100644
--- a/include/dwarf2.h
+++ b/include/dwarf2.h
@@ -474,6 +474,7 @@ enum d
