Revision tags: v6.2.1, v6.2.0, v6.3.0, v6.0.1, v6.0.0, v6.0.0rc1, v6.1.0, v5.8.3, v5.8.2, v5.8.1, v5.8.0, v5.9.0, v5.8.0rc1, v5.6.3, v5.6.2, v5.6.1, v5.6.0, v5.6.0rc1, v5.7.0, v5.4.3, v5.4.2 |
|
#
df642abc |
| 20-Mar-2019 |
zrj <rimvydas.jasinskas@gmail.com> |
gcc80: Add local -save-temps=objects option.
The gcc currently supports -save-temps= cwd, obj, object(not documented). None of those variants can be used at all during buildworld sequence, even at s
gcc80: Add local -save-temps=objects option.
The gcc currently supports -save-temps= cwd, obj, object(not documented). None of those variants can be used at all during buildworld sequence, even at serial buildworld, without interfering with build in funny ways. This is very easy to notice while compiling libraries, where rules are: * foo.c --> foo.o (non-pic) * foo.c --> foo.So (pic) * foo.c --> foo.po (profiled)
The added option forces to use full object name (if it was supplied) when constructing names for .s and .i intermediates, as follows: cc -c foo.c -o foo.o --> foo.o.s + foo.o.i This allows to use -save-temps globally during buildworld and it is *less* likely to interfere while producing normally created objects. Repeated quickworld likely *will* have side effects, because the '-o' flags are not used for kernel and programs (foo.s will shadow foo.c).
Tested by binary comparing /usr/obj trees for differences.
show more ...
|
Revision tags: v5.4.1, v5.4.0, v5.5.0, v5.4.0rc1, v5.2.2, v5.2.1 |
|
#
38fd1498 |
| 02-May-2018 |
zrj <rimvydas.jasinskas@gmail.com> |
Import GCC-8 to a new vendor branch
|
#
632577db |
| 02-May-2018 |
zrj <rimvydas.jasinskas@gmail.com> |
gcc80: Adjust search paths for base compiler layout.
All tools are located in a common /usr/libexec/gcc80/ directory.
|