7423731691
For the 32-bit targets the limitations of the object file format (e.g. 32-bit ELF) will not allow > 2GiB debug info anyway, and as I've just tested, e.g. on x86_64 with -m32 -gdwarf64 will not work even on tiny testcases: as: pr64716.o: unsupported relocation type: 0x1 pr64716.s: Assembler messages: pr64716.s:6013: Error: cannot represent relocation type BFD_RELOC_64 as: pr64716.o: unsupported relocation type: 0x1 pr64716.s:6015: Error: cannot represent relocation type BFD_RELOC_64 as: pr64716.o: unsupported relocation type: 0x1 pr64716.s:6017: Error: cannot represent relocation type BFD_RELOC_64 So yes, we can either do a sorry, error, or could just avoid 64-bit relocations (depending on endianity instead of emitting .quad expression_that_needs_relocation emit .long expression_that_needs_relocation, 0 or .long 0, expression_that_needs_relocation This patch implements that last option, dunno if we need also configure tests for that or not, maybe some 32-bit targets use 64-bit ELF and can handle such relocations. > 64bit relocs are not required here? That is, can one with > dwarf64 choose 32bit forms for select offsets (like could > dwz exploit this?)? I guess it depends on whether for 32-bit target and -gdwarf64, when calling dw2_assemble_integer with non-CONST_INT argument we only need positive values or might need negative ones too. Because positive ones can be easily emulated through that .long expression, 0 or .long 0, expression depending on endianity, but I'm afraid there is no way to emit 0 or -1 depending on the sign of expression, when it needs relocations. Looking through dw2_asm_output_delta calls, at least the vast majority of the calls seem to guarantee being positive, not 100% sure about one case in .debug_line views, but I'd hope it is ok too. In most cases, the deltas are between two labels where the first one in the arguments is later in the same section than the other one, or where the second argument is the start of a section or another section base. 2021-01-26 Jakub Jelinek <jakub@redhat.com> * dwarf2asm.c (dw2_assemble_integer): Handle size twice as large as DWARF2_ADDR_SIZE if x is not a scalar int by emitting it as two halves, one with x and the other with const0_rtx, ordered depending on endianity. |
||
|---|---|---|
| c++tools | ||
| config | ||
| contrib | ||
| fixincludes | ||
| gcc | ||
| gnattools | ||
| gotools | ||
| include | ||
| INSTALL | ||
| intl | ||
| libada | ||
| libatomic | ||
| libbacktrace | ||
| libcc1 | ||
| libcody | ||
| libcpp | ||
| libdecnumber | ||
| libffi | ||
| libgcc | ||
| libgfortran | ||
| libgo | ||
| libgomp | ||
| libhsail-rt | ||
| libiberty | ||
| libitm | ||
| libobjc | ||
| liboffloadmic | ||
| libphobos | ||
| libquadmath | ||
| libsanitizer | ||
| libssp | ||
| libstdc++-v3 | ||
| libvtv | ||
| lto-plugin | ||
| maintainer-scripts | ||
| zlib | ||
| .dir-locals.el | ||
| .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 | ||
| 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.