This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [patch] Do not generate discriminator directive in strict mode
- From: Eric Botcazou <ebotcazou at adacore dot com>
- To: Richard Henderson <rth at redhat dot com>
- Cc: gcc-patches at gcc dot gnu dot org
- Date: Wed, 20 Apr 2011 21:09:26 +0200
- Subject: Re: [patch] Do not generate discriminator directive in strict mode
- References: <201104191540.18889.ebotcazou@adacore.com> <4DAF1CFF.1@redhat.com>
> How is this not redundant with the existing
>
> /* The discriminator column was added in dwarf4. Simplify the below
> by simply removing it if we're not supposed to output it. */
> if (dwarf_version < 4 && dwarf_strict)
> discriminator = 0;
>
> check near the top of the function?
Obviously I missed this recent change, sorry. So the question is: would the
change be appropriate for the release branches, where we emit the directive
unconditionally, i.e 4.5 and 4.6 branches, or would mine be safer for them?
This directive apparently confuses (some versions of) the Wind River debugger.
--
Eric Botcazou