From: Simon Marchi <simon.marchi@polymtl.ca>
To: gdb-patches@sourceware.org, Tom Tromey <tom@tromey.com>
Subject: Re: [PATCH v2 0/3] Poison obstack functions
Date: Mon, 21 May 2018 03:23:00 -0000 [thread overview]
Message-ID: <c6cc5e48-3c61-b36b-6daf-4080911677a1@polymtl.ca> (raw)
In-Reply-To: <574e2d68-3f8c-fc42-2834-e6c921413c4b@polymtl.ca>
On 2018-05-20 09:10 PM, Simon Marchi wrote:
> Since Tom is playing with some things that are obstack allocated in dwarf2read, I
> finally pushed this in case it helps.
I forgot to mention that I did not push patch 1 because it was obsoleted by a similar
patch from Tom.
Simon
next prev parent reply other threads:[~2018-05-21 1:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-28 3:31 Simon Marchi
2018-04-28 3:31 ` [PATCH v2 1/3] Don't allocate mapped_index on the objfile obstack Simon Marchi
2018-04-28 3:31 ` [PATCH v2 3/3] Use XOBNEW/XOBNEWVEC/OBSTACK_ZALLOC when possible Simon Marchi
2018-04-28 3:31 ` [PATCH v2 2/3] Introduce obstack_new, poison other "typed" obstack functions Simon Marchi
2018-05-21 3:00 ` [PATCH v2 0/3] Poison " Simon Marchi
2018-05-21 3:23 ` Simon Marchi [this message]
2018-05-21 8:53 ` [pushed] Fix copy-pasto, allocate objfile_per_bfd_storage with obstack_new Simon Marchi
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=c6cc5e48-3c61-b36b-6daf-4080911677a1@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.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