mirror of
https://gcc.gnu.org/git/gcc.git
synced 2026-06-10 13:59:42 +00:00
TEMPORARY mirror of https://gcc.gnu.org/git/gcc.git for https://forge.sourceware.org/ experimenting.
...
DO NOT FORK THIS REPO! You want to fork https://forge.sourceware.org/gcc/gcc-TEST instead.
...
Read https://gcc.gnu.org/wiki/ForgeExperiment first.
https://gcc.gnu.org
- C++ 30.7%
- C 30.2%
- Ada 14.3%
- D 6.1%
- Go 5.7%
- Other 12.5%
2b3402f565
I was testing spec2017 late last week on the K3 design and stumbled across a couple of functional fails. In this particular case we mis-compiled omnet, thankfully in such a way that it didn't really run at all, so time to failure was exceedingly short. A couple months ago I extended our ability to recognize more czero sequences, particularly in cases where we're combining the output of 2 or more sCC style insns. I took a bit of a short-cut and adjusted the code on a node I knew would not be shared in the IL when doing a split. I should have known better. PUT_MODE and PUT_CODE are generally bad to use and I've called out others for similar changes. Consider if we're doing a 3->2 split, but when one of the two split insns do not match. In that scenario the PUT_CODE trick is going to cause problems because we change the IL, but the transformation as a whole isn't applied. In this case we're inverting the mode (EQ->NE and NE->EQ), the net is we flip the tense of a branch/sCC. I never narrowed down a testcase. This was found by inspecting codegen and dump differences after bisecting to a change and bisecting down to a single .o file. This fixes the omnet failure. There's a second cluster of failures (502.gcc) which are unrelated and I'm still debugging those failures. Bootstrapped and regression tested on riscv64. Of course the original patch survived that test as well, so perhaps take it with a mountain of salt rather than the usual grain... Waiting on pre-commit before moving forward. * config/riscv/zicond.md (combined sCC splitters): Avoid using PUT_MODE to change existing RTL. Instead just generate a new node. |
||
|---|---|---|
| .forgejo | ||
| .github | ||
| c++tools | ||
| config | ||
| contrib | ||
| fixincludes | ||
| gcc | ||
| gnattools | ||
| gotools | ||
| include | ||
| INSTALL | ||
| libada | ||
| libatomic | ||
| libbacktrace | ||
| libcc1 | ||
| libcody | ||
| libcpp | ||
| libdecnumber | ||
| libffi | ||
| libga68 | ||
| libgcc | ||
| libgcobol | ||
| libgfortran | ||
| libgm2 | ||
| libgo | ||
| libgomp | ||
| libgrust | ||
| libiberty | ||
| libitm | ||
| libobjc | ||
| libphobos | ||
| libquadmath | ||
| libsanitizer | ||
| libssp | ||
| libstdc++-v3 | ||
| libvtv | ||
| lto-plugin | ||
| maintainer-scripts | ||
| zlib | ||
| .b4-config | ||
| .dir-locals.el | ||
| .editorconfig | ||
| .gitattributes | ||
| .gitignore | ||
| ABOUT-NLS | ||
| ar-lib | ||
| ChangeLog | ||
| ChangeLog.jit | ||
| ChangeLog.tree-ssa | ||
| compile | ||
| config-ml.in | ||
| config.guess | ||
| config.rpath | ||
| config.sub | ||
| configure | ||
| configure.ac | ||
| COPYING | ||
| COPYING.LIB | ||
| COPYING.RUNTIME | ||
| COPYING3 | ||
| COPYING3.LIB | ||
| depcomp | ||
| install-sh | ||
| libtool-ldflags | ||
| libtool.m4 | ||
| ltgcc.m4 | ||
| ltmain.sh | ||
| ltoptions.m4 | ||
| ltsugar.m4 | ||
| ltversion.m4 | ||
| lt~obsolete.m4 | ||
| MAINTAINERS | ||
| Makefile.def | ||
| Makefile.in | ||
| Makefile.tpl | ||
| missing | ||
| mkdep | ||
| mkinstalldirs | ||
| move-if-change | ||
| multilib.am | ||
| README | ||
| SECURITY.txt | ||
| symlink-tree | ||
| test-driver | ||
| ylwrap | ||
This directory contains the GNU Compiler Collection (GCC). The GNU Compiler Collection is free software. See the files whose names start with COPYING for copying permission. The manuals, and some of the runtime libraries, are under different terms; see the individual source files for details. The directory INSTALL contains copies of the installation information as HTML and plain text. The source of this information is gcc/doc/install.texi. The installation information includes details of what is included in the GCC sources and what files GCC installs. See the file gcc/doc/gcc.texi (together with other files that it includes) for usage and porting information. An online readable version of the manual is in the files gcc/doc/gcc.info*. See http://gcc.gnu.org/bugs/ for how to report bugs usefully. Copyright years on GCC source files may be listed using range notation, e.g., 1987-2012, indicating that every year in the range, inclusive, is a copyrightable year that could otherwise be listed individually.