Re: Information about .debug and .line section in elf files
Michael Eager wrote: > Oliver Eichler wrote: >> Hi, >> >> as the subjects states I try to find information about the .debug and >> .line section in elf files. My elf files are build with gcc for ARC. The >> elf man page is quite sparse about these sections. Can anyone give me a >> hint where to find more information? Or where to look within the gcc >> source for stucture definitions. > > These sections contain DWARF debugging information. > Ahhh, that's where the DWARF stuff goes. You are right it's DWARF 1.1 coded. Always thought DWARF is an own file format :). Thanks Oliver > You can find documentation about DWARF at dwarf.freestandards.org. > -- Ingenieure Kellermann, Voigt, Hoepfl, Eichler und Weidner, Partnerschaft DSP Solutions http://www.dspsolutions.de
Notes of the libgcc-math BOF at the summit.
Issues of providing both standard conforming and target optimized math runtimes for GCC were discussed. Interested parties are various frontends (C++, Fortran, Ada) that are required to provide support similar to C99 from their runtime and like to be able to fall back to a standard conforming implementation provided by GCC. Especially on weird target architectures and OSs where the existing runtime is only partly working or cannot be relied upon. Other interest is from folks that require optimized versions of the math runtime, being it for different ABI, stripped versions useful for -ffast-math or -fno-math-errno. In addition to that, a place to add vectorized versions of the math routines, which are closely integrated to GCC is requested. Several points were be made about licensing, and people agreed that while it may be possible to use the LGPL, using GPL + exception will avoid user confusion and possible problems, especially if we are going to automatically link against this library. People had concerns about forking GNUs libm from glibc with respect to maintainance issues. The point was made that the standard conforming runtime GCC would provide was optional and not to be used if there is a conforming (and performant) runtime available from glibc or the target. Only the optimized routines would be used on such systems, which of course, if target dependent would have to be provided by the architecture maintainers if they want to enable extra optimizations for their platform. There were no doubts that we can get hands on properly licensed (GPL + exception compatible) standard conforming C routines that implement the C99 math runtime. Offerings were from AMD, and the original BSD-licensed routines from SUN were mentioned. Also it was suggested IBM could re-submit their math library for use in GCC with a GPL + exception license. -- In conclusion, having a C99 math runtime subject to GPL + exception inside GCC alongside with whatever optimized routines (being able to base on the C routines provided by the C99 routines) was generally accepted as worthwhile. Thanks, Richard. PS: please direct discussion to gcc@gcc.gnu.org only and avoid cross-posting followups.
Notes from the BOF on DFP on x86/x86-64 at the GCC Summit
A proposal was made to pick one the Decimal Floating-Point encodings from the IEEE754r draft in the x86-64 psABI a few weeks ago (see thread starting at http://www.amd64.org/lists/discuss/thrd215.html#08857). Given that any such decision can have multiple developments, many users of x86-64 were invited to discuss this proposal in the [EMAIL PROTECTED] mailing-list. Taking the opportunity that many x86-64 users were at the GCC Summit, including some already taking part in this discussion, we set up a BOF session to exchange ideas on DFP in x86-64 and even in GCC. I posted a summary at http://www.amd64.org/lists/discuss/maillist.html (archive will be updated momentarily). Please, feel free to correct or complement my summary. All are invited to continue this discussion at the [EMAIL PROTECTED] mailing-list (subscribe at http://www.amd64.org/mailinglists). -- ___ Evandro Menezes AMDAustin, TX
gcc-4.1-20060630 is now available
Snapshot gcc-4.1-20060630 is now available on ftp://gcc.gnu.org/pub/gcc/snapshots/4.1-20060630/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 4.1 SVN branch with the following options: svn://gcc.gnu.org/svn/gcc/branches/gcc-4_1-branch revision 115107 You'll find: gcc-4.1-20060630.tar.bz2 Complete GCC (includes all of below) gcc-core-4.1-20060630.tar.bz2 C front end and core compiler gcc-ada-4.1-20060630.tar.bz2 Ada front end and runtime gcc-fortran-4.1-20060630.tar.bz2 Fortran front end and runtime gcc-g++-4.1-20060630.tar.bz2 C++ front end and runtime gcc-java-4.1-20060630.tar.bz2 Java front end and runtime gcc-objc-4.1-20060630.tar.bz2 Objective-C front end and runtime gcc-testsuite-4.1-20060630.tar.bz2The GCC testsuite Diffs from 4.1-20060623 are available in the diffs/ subdirectory. When a particular snapshot is ready for public consumption the LATEST-4.1 link is updated and a message is sent to the gcc list. Please do not use a snapshot before it has been announced that way.
explaination of some gcc functions
hi, I'm trying to understand the backend code of gcc for MIPS architecture.I'm having some trouble while understanding following functions. 1: push_topmost_sequence(); 2: emit_insn_after(seq,get_insns()); 3: pop_topmost_sequence(); 4: emit_insn_before Would you please explain what's the role of each function.
