This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Using libbacktrace in libgfortran: some questions

From: Ian Lance Taylor <iant at google dot com>
To: FX <fxcoudert at gmail dot com>
Cc: Ian Lance Taylor <ian at airs dot com>, GCC Development <gcc at gcc dot gnu dot org>, gfortran <fortran at gcc dot gnu dot org>, gcc-patches <gcc-patches at gcc dot gnu dot org>
Date: Thu, 13 Aug 2015 15:56:04 -0700
Subject: Re: Using libbacktrace in libgfortran: some questions
Authentication-results: sourceware.org; auth=none
References: <8880A586-94DE-4745-B2BD-E07582E0F1DD at gmail dot com> <m3r3n7l2vb dot fsf at pepe dot airs dot com> <36782CE5-FAB5-4651-92B1-0A5C5C0B422A at gmail dot com> <5BD9B520-145D-4806-BBAD-1D003465CB1A at gmail dot com> <CAKOQZ8zPwKjU+L20xCsSVm6DrC619LPdrOHEh+TjtHAHuABU=A at mail dot gmail dot com> <CAKOQZ8xi5MF_N2Yeh-rQU6is=8XV_nxWQ50Fv_btri__iUdZVg at mail dot gmail dot com> <DEB0FDF5-882E-45DC-9C12-52FBFF68077E at gmail dot com>

On Thu, Aug 13, 2015 at 8:50 AM, FX <fxcoudert@gmail.com> wrote:
>> And yet, that patch has absolutely nothing to do with libbacktrace.
>> Hmmm.  Let's try this one.
>
> Works perfectly with the patch:

Patch tested and committed with this ChangeLog entry.

2015-08-13  Ian Lance Taylor  <iant@google.com>

* dwarf.c (read_function_entry): Add vec_inlined parameter.
Change all callers.

Attachment: patch.txt
Description: Text document

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]