This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [google] Allow relative profile paths. (issue4280074)
- From: dnovillo at google dot com
- To: martint at google dot com
- Cc: gcc-patches at gcc dot gnu dot org, reply at codereview dot appspotmail dot com
- Date: Mon, 28 Mar 2011 17:59:32 +0000
- Subject: Re: [google] Allow relative profile paths. (issue4280074)
- Reply-to: martint at google dot com, dnovillo at google dot com, gcc-patches at gcc dot gnu dot org, reply at codereview dot appspotmail dot com
OK. A nit and a question below.
Diego.
http://codereview.appspot.com/4280074/diff/1/gcc/doc/invoke.texi
File gcc/doc/invoke.texi (right):
http://codereview.appspot.com/4280074/diff/1/gcc/doc/invoke.texi#newcode7777
gcc/doc/invoke.texi:7777: and its related options. Both absolute and
relative can be used.
s/relative/relative paths/
http://codereview.appspot.com/4280074/diff/1/gcc/libgcov.c
File gcc/libgcov.c (right):
http://codereview.appspot.com/4280074/diff/1/gcc/libgcov.c#newcode286
gcc/libgcov.c:286: if (prefix_length != 0 && !IS_DIR_SEPARATOR (*fname))
I'm confused. why did you take !HAS_DRIVE_SPEC() out?
http://codereview.appspot.com/4280074/