aboutsummaryrefslogtreecommitdiff
path: root/gcc/rust/backend/rust-compile-base.h
diff options
context:
space:
mode:
authorStefan Schulze Frielinghaus <stefansf@gcc.gnu.org>2025-03-20 16:48:24 +0100
committerStefan Schulze Frielinghaus <stefansf@gcc.gnu.org>2025-03-20 16:48:24 +0100
commit81166d54ca1b3a21bad387a862a87be9c389ac92 (patch)
tree8521b55ee554700c249f65e94665463effa8caf8 /gcc/rust/backend/rust-compile-base.h
parenta1363f8dd8037d40e9fbf04c2ba8d6d3e7e5c269 (diff)
downloadgcc-81166d54ca1b3a21bad387a862a87be9c389ac92.zip
gcc-81166d54ca1b3a21bad387a862a87be9c389ac92.tar.gz
gcc-81166d54ca1b3a21bad387a862a87be9c389ac92.tar.bz2
Revert "s390: Deprecate ESA/390 support"
The intention of -m31 -mesa and -m31 -mzarch was that they are (ABI) compatible which is almost true except as it turns out they are not for attribute mode(word). After doing some archaeology and digging out an over 18 year old thread [1,2] which is about this very attribute, I come to the conclusion to revert this patch. The intention by deprecating and eventually removing ESA/390 support was to prepare for a future removal of -m31; though in smaller steps. Thus, instead of introducing some potential hick ups along the route, I will revert this patch and will revisit this topic when time for -m31 in its entirety has come---independent of -mesa/-mzarch. [1] https://gcc.gnu.org/pipermail/gcc-patches/2006-September/200465.html [2] https://gcc.gnu.org/pipermail/gcc-patches/2006-October/201154.html This reverts commit 3b1bd1fdcd241dd1e5b706b6937400d74ca43146.
Diffstat (limited to 'gcc/rust/backend/rust-compile-base.h')
0 files changed, 0 insertions, 0 deletions