Displaying 10 results from an estimated 10 matches for "csabaraduli".
Did you mean:
csabaraduly
2019 Mar 29
2
Test failure due to file path
Hi all,
The following tests fail because my username (csabaraduly) contains "bar" :
********************
FAIL: LLVM :: tools/llvm-objcopy/ELF/regex.test (47099 of 50832)
******************** TEST 'LLVM :: tools/llvm-objcopy/ELF/regex.test'
FAILED ********************
Script:
--
: 'RUN: at line 1';
/home/csabaraduly/wk/LLVM-git/__build_release_99/bin/yaml2obj
2019 Mar 29
2
Test failure due to file path
For ignore-undefined-symbols.s, the simplest fix ought to be to have the llvm-mc RUN line take the source from <stdin>:
# RUN: llvm-mc –filetype=obj –triple=x86_64-pc-linux %s –o %t.o –g
becomes
# RUN: llvm-mc –filetype=obj –triple=x86_64-pc-linux < %s –o %t.o –g
But in this case, llvm-symbolizer still prints the file as $CWD/<stdin> which seems like its own separate bug.
--paulr
2013 Jun 07
0
[LLVMdev] Build failure (tblgen crash) on Ubuntu
Hi all,
I'm building clang on Ubuntu LTS 12.04 and it started blowing up since
yesterday:
$ make update
svn update /home/csabaraduly/workspace/LLVM/llvm
At revision 183495.
At revision 183495.
At revision 183495.
At revision 183495.
$ make all VERBOSE=1
for dir in lib/Support lib/TableGen utils lib/IR lib tools/llvm-config
tools runtime docs unittests; do \
if ([ ! -f $dir/Makefile ] ||
2018 Apr 16
2
tools/llvm-dwarfdump/X86/debug-names-find.s spurious failure
********************
FAIL: LLVM :: tools/llvm-dwarfdump/X86/debug-names-find.s (38881 of 41794)
******************** TEST 'LLVM ::
tools/llvm-dwarfdump/X86/debug-names-find.s' FAILED
********************
Script:
--
/home/csabaraduly/wk/LLVM/build_release/bin/llvm-mc -triple
x86_64-pc-linux
/home/csabaraduly/wk/LLVM/llvm/test/tools/llvm-dwarfdump/X86/debug-names-find.s
-filetype=obj -o
2018 Apr 16
0
tools/llvm-dwarfdump/X86/debug-names-find.s spurious failure
Hello Csaba,
Thanks for the heads up. I am the one who wrote that test. I'll look into
that shortly. Sorry about the trouble.
pl
On Mon, 16 Apr 2018 at 11:56, Csaba Raduly via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> ********************
> FAIL: LLVM :: tools/llvm-dwarfdump/X86/debug-names-find.s (38881 of 41794)
> ******************** TEST 'LLVM ::
>
2018 Apr 16
1
tools/llvm-dwarfdump/X86/debug-names-find.s spurious failure
r330121 should fix that. Let me know if you still run into any issues.
cheers,
pl
On Mon, 16 Apr 2018 at 12:07, Pavel Labath <labath at google.com> wrote:
> Hello Csaba,
> Thanks for the heads up. I am the one who wrote that test. I'll look into
> that shortly. Sorry about the trouble.
> pl
> On Mon, 16 Apr 2018 at 11:56, Csaba Raduly via llvm-dev <
> llvm-dev at
2014 Nov 18
2
[LLVMdev] Test failure
Hi,
For a couple of days now, one of the tests fails:
FAIL: LLVM :: MC/R600/sopp.s (16225 of 19902)
******************** TEST 'LLVM :: MC/R600/sopp.s' FAILED ********************
Script:
--
/home/csabaraduly/workspace/LLVM/build/Release+Asserts/bin/llvm-mc
-arch=r600 -mcpu=SI -show-encoding
/home/csabaraduly/workspace/LLVM/llvm/test/MC/R600/sopp.s |
2017 Nov 27
2
Go Tsan check failure
Hi all,
I'm trying to build clang on Ubuntu 17.10 - the build succeeds, but
testing fails:
~/wk/LLVM/build_release$ svn info ../llvm/
Path: /home/csabaraduly/wk/LLVM/llvm
Working Copy Root Path: /home/csabaraduly/wk/LLVM/llvm
URL: https://llvm.org/svn/llvm-project/llvm/trunk
Relative URL: ^/llvm/trunk
Repository Root: https://llvm.org/svn/llvm-project
Repository UUID:
2017 Nov 28
2
Go Tsan check failure
On Tue, Nov 28, 2017 at 12:16 AM, Kostya Serebryany <kcc at google.com> wrote:
> +dvyukov
>
> On Mon, Nov 27, 2017 at 4:56 AM, Csaba Raduly via llvm-dev
> <llvm-dev at lists.llvm.org> wrote:
>>
>> Hi all,
>>
>> I'm trying to build clang on Ubuntu 17.10 - the build succeeds, but
>> testing fails:
>>
>> ~/wk/LLVM/build_release$
2017 Nov 28
1
Go Tsan check failure
I guess there is lots of stuff that you don't care about besides
tsan/go that is built and tested during llvm build, and there is no
way to selectively disable each one of that. By design.
In the long run we need to fix all failures (please file a proper
bug). If you are looking for a temporal workaround, then comment it
out. I don't what else to suggest.
On Tue, Nov 28, 2017 at 9:47 AM,