This is the mail archive of the 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: output directory for -fvtv-debug and -fvtv-counts

Hi Sandra,

Thank you for fixing this documentation.  The code got updated a  bit
after this was written and I forgot to update that.   The log files no
longer go into "the dump file directory on the user's machine".
Instead, this option checks to see if there is an environment variable
VTV_LOGS_DIR that has been defined.  If that variable exists, then the
log files are written there; otherwise they go into the current
working directory.

Let me know if you have any other questions, and thank you for doing this!

-- Caroline Tice

On Wed, Dec 31, 2014 at 12:03 PM, Sandra Loosemore
<> wrote:
> I noticed that the documentation for the -fvtv-* options in invoke.texi
> needed a little copy-editing and markup correction.  I started working on a
> patch, but I'm stuck on this:
> The documentation currently says the compile-time log files for these
> options are written in "the dump file directory on the user's machine".
> Where, exactly, is this supposed to be?  From reading the code, it looks
> like the default is the current directory rather than the directory of the
> output file (the default for the -fdump-* options).  Is this difference
> intentional?  If so, can the documentation just say it's written to the
> current directory?  Alternatively, the option that controls this, -dumpdir,
> is not documented in invoke.texi; should it be, or is this (and its
> similarly undocumented friend -dumpbase) strictly an internal option for
> communication between the GCC driver and subprocesses, or something like
> that?
> -Sandra

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