139f99c058
Changes compared to GCC 7.x 001-revert_register_mode_search.patch dropped The underlying issue is described at the end of https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58139 It is fixed by the upstream commit:3fa2798aa8020-PR-libstdc-81797-Add-.NOTPARALLEL-to-include-Makefil.patch dropped due to already upstream 100-PR-rtl-optimization-83496.patch dropped due to already upstream 910-mbsd_multi.patch modified to fix ambiguous overloaded inform() call error gcc/input.h header: define UNKNOWN_LOCATION ((source_location) 0) - inform (0, "someone does not honour COPTS correctly, passed %d times", - honour_copts); + inform (UNKNOWN_LOCATION, "someone does not honour COPTS correctly, passed %d times", + honour_copts); 940-no-clobber-stamp-bits.patch dropped due to fixed upstream by another way upstream commit:87b2d547f8950-cpp_file_path_translation.patch dropped, Both -fmacro-prefix-map and -ffile-prefix-map are added to gcc 8.1.0, if I understand it correctly, we should use -fmacro-prefix-map usage: -fmacro-prefix-map=@var{old}=@var{new} upstream commit:859b51f836-iremap exists as a flag for a long time, for backward compatibility, I think we should keep the variable name unchanged but change its value in rules.mk for gcc 8.x and higher. Compile and run tested on x86_64 Signed-off-by: Syrone Wong <wong.syrone@gmail.com>
22 lines
690 B
Diff
22 lines
690 B
Diff
Author: Jo-Philipp Wich <jow@openwrt.org>
|
|
Date: Sat Apr 21 03:02:39 2012 +0000
|
|
|
|
gcc: add patch to make the getenv() spec function nonfatal if requested environment variable is unset
|
|
|
|
SVN-Revision: 31390
|
|
|
|
--- a/gcc/gcc.c
|
|
+++ b/gcc/gcc.c
|
|
@@ -9347,8 +9347,10 @@ getenv_spec_function (int argc, const ch
|
|
value = varname;
|
|
|
|
if (!value)
|
|
- fatal_error (input_location,
|
|
- "environment variable %qs not defined", varname);
|
|
+ {
|
|
+ warning (input_location, "environment variable %qs not defined", varname);
|
|
+ value = "";
|
|
+ }
|
|
|
|
/* We have to escape every character of the environment variable so
|
|
they are not interpreted as active spec characters. A
|