similar to: [LLVMdev] Unreachable in llvm-nm in Debug mode

Folks, I'm seeing this unreachable on test/Object/archive-symtab.test in debug mode: $ /home/rengolin/workspace/llvm/bin/./llvm-nm -s /home/rengolin/workspace/llvm/test/Object/Output/archive-symtab.test.tmp.a trivial-object-test.elf-x86-64: U SomeOtherFunction 00000000 T main U puts Invalid alignment for ELF file! UNREACHABLE executed at

I've also been looking at debugging with ELF and noticed the same problem as Renato. I just sent a patch to llvmcommits that fixes the problem. DW_at_stmt_list needs to emit a label(and therefore a relocation) for the offset rather a constant 0, then the linker can fixup the offset as it shuffles object files around. Krister On Thu, Aug 26, 2010 at 5:11 AM, Renato Golin <rengolin at

On Wed, Oct 12, 2011 at 3:17 AM, Songmao <smtian at ingenic.cn> wrote: > Michael, >    I have rework the patch according to your suggestion.  And I have read > binutil/objdump source code and found that it has a logic that if there's no > symtab, it will use dynsym, which is missing in llvm-objdump. > > Songmao > @@ -747,12 +747,28 @@ error_code

2012/1/23 Bendersky, Eli <eli.bendersky at intel.com>: > Hi, > > I would like to examine the implications you mention in more detail. > Thank you! > (1) Symbol address > According to the ELF standard, in a symbol table entry st_value means: "In relocatable files, st_value holds a section offset for a defined symbol. That is, > st_value is an offset from the

Hi, I would like to examine the implications you mention in more detail. (1) Symbol address According to the ELF standard, in a symbol table entry st_value means: "In relocatable files, st_value holds a section offset for a defined symbol. That is, st_value is an offset from the beginning of the section that st_shndx identifies." (*) Therefore, when queried about a symbol's

See "DwarfDebug problem with line section" thread on llvmdev. Bottom line, we may need a target specific patch for targets that do not follow dwarf standard (as per my reading) in this particular case. - Devang On Wed, Aug 25, 2010 at 5:49 AM, Renato Golin <rengolin at systemcall.org>wrote: > Hi, > > I'm trying to compile two files together with debug information

On 25 August 2010 18:54, Devang Patel <devang.patel at gmail.com> wrote: > See "DwarfDebug problem with line section" thread on llvmdev. Bottom line, > we may need a target specific patch for targets that do not follow dwarf > standard (as per my reading) in this particular case. Hi Devang, Ok, got the background, but will reply on this email. As far as I understood,

Michael, I have rework the patch according to your suggestion. And I have read binutil/objdump source code and found that it has a logic that if there's no symtab, it will use dynsym, which is missing in llvm-objdump. Songmao -------------- next part -------------- A non-text attachment was scrubbed... Name: 0002-Fix-the-address-calculation-for-llvm-objdump.patch Type: text/x-patch

On 25 Sep 2013, at 22:22, Renato Golin <renato.golin at linaro.org> wrote: > Documentations get outdated more often than comments in the code, and LLVM is particularly good at generic comments, but not so much at teaching how to use the code. > > Patches adding comments are also a good way to learn how something works. You send a comment, people say how wrong that is, and in the

While working on some other changes I came across a problem where ELFObjectFile::getSymbolFileOffset was returning a different value than I expected in the case where the symbol in question was a section. Looking at the code, it seems obviously wrong, but I didn't want to just commit my change without at least asking if anyone knew of a good reason for the current behavior. I know there

On Fri, Oct 26, 2012 at 2:53 PM, Renato Golin <rengolin at systemcall.org> wrote: > Hi, > > I'm trying to setup the test-suite and am getting short of running it... > > Following the steps here: > > http://llvm.org/docs/lnt/quickstart.html > > I got as far as getting lnt installed, but when I run the "lnt runtest > nt" it fails: > >

I hit the same problems as you did when I tried it a few weeks ago. Haven't bothered with it since. There is a way to run tests without using lnt. You can use the Makefiles directly in your test-suite build directory. For running nightly tests, you can do: make report.html TEST=nightly That will generate a html file with the test results in. Amara On 26 October 2012 22:53, Renato Golin

> There is no need for emitting the full symtab. I checked the overhead with a huge internal C++ source. The overhead of symtab + str table compared with byte code with debug is about 3%. It's still sizable and could be noticeable if thinLTO can deliver compile times that closer to what resembles builds without LTO as your results suggest. > More importantly, it is also possible to use

On Mon, Jun 1, 2015 at 6:34 AM, Teresa Johnson <tejohnson at google.com> wrote: > On Fri, May 29, 2015 at 6:15 PM, Sean Silva <chisophugis at gmail.com> wrote: > > > > > > On Fri, May 29, 2015 at 8:01 AM, Teresa Johnson <tejohnson at google.com> > > wrote: > >> > >> On Fri, May 29, 2015 at 6:56 AM, Alex Rosenberg <alexr at

I will be there again! On 30 July 2012 10:35, Renato Golin <rengolin at systemcall.org> wrote: > On 30 July 2012 09:34, Renato Golin <rengolin at systemcall.org> wrote: > > The tentative date for the next Cambridge LLVM Social is Wed 22nd > > October, 7:30pm at the Cambridge Blue. > > Of course, I meant August. Thanks Igor for the correction!! > > -- >

Hi Renato, You're right it's VMLA/VMLS that are generated. Still don't understand what drives generation for Cortex-A9. I was using fmac for floating point MAC not for fused MAC. Than I realized that we spoke about fma instead of fmac. So back to the original problem why when using -mcpu=cortex-a9 VMLA/VMLS are not generated and when I use -mtriple=armv7-eabi they are ? Best

Exactly how are you running the tests? Via LNT or directly? If via LNT, make sure you test suite repository is clean (no in tree configure or make results). - Daniel On Oct 28, 2012, at 9:57, Renato Golin <rengolin at systemcall.org> wrote: > Round 2, fight! > > I managed to run many tests (not sure all of them), and some failed, > some didn't. All errors in the

Hi Shankar, On Tue, Feb 12, 2013 at 10:46 PM, Shankar Easwaran <shankare at codeaurora.org> wrote: > Author: shankare > Date: Tue Feb 12 12:46:53 2013 > New Revision: 174990 > > URL: http://llvm.org/viewvc/llvm-project?rev=174990&view=rev [...] > ELFDefinedAtom<ELFT> *createDefinedAtomAndAssignRelocations( > StringRef symbolName, StringRef

On Mon, Dec 31, 2012 at 6:09 PM, Renato Golin <rengolin at systemcall.org> wrote: >> 1. checkout master and pull from origin. >> 2. rebase stuff to be committed onto master. > > Can you commit directly from branches? Or do you have to merge to > master to commit? I believe that what git-svn does is commit everything in your branch that isn't in mainline (i.e.

My earlier statement about wrapping things in a native object file held in that it is controversial. It appears to be still central to your design. It may help to look at the problem from a different viewpoint: LLVM is not a compiler. It is a framework that can be used to make compiler-like tools. >From that view, it no longer makes sense to discuss "the plugin," or gold, or $AR,