Arnout Vandecappelle 2f8dc29c1d gcc: remove unsafe patch check (poison system dirs) patch ... Now that the calls to gcc always pass through the toolchain wrapper, it is no longer necessary to patch gcc to support poisoning. This does have the disadvantage that there is no unsafe path check for libc, libgcc and libstdc++ (all of these are built before the wrapper exists). But we can assume that the toolchain components themselves should be pretty safe. Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Reviewed-by: Romain Naour <romain.naour@openwide.fr> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>		2015-10-04 18:22:20 +02:00
..
4.5.4
4.7.4	gcc: remove unsafe patch check (poison system dirs) patch	2015-10-04 18:22:20 +02:00
4.8.5	gcc: remove unsafe patch check (poison system dirs) patch	2015-10-04 18:22:20 +02:00
4.9.3	gcc: remove unsafe patch check (poison system dirs) patch	2015-10-04 18:22:20 +02:00
5.2.0	gcc: remove unsafe patch check (poison system dirs) patch	2015-10-04 18:22:20 +02:00
arc-2015.06	gcc: remove unsafe patch check (poison system dirs) patch	2015-10-04 18:22:20 +02:00
gcc-final	gcc: remove unsafe patch check (poison system dirs) patch	2015-10-04 18:22:20 +02:00
gcc-initial	gcc: use toolchain wrapper	2015-10-04 18:22:20 +02:00
Config.in.host
gcc.hash
gcc.mk	gcc: use toolchain wrapper	2015-10-04 18:22:20 +02:00