Page MenuHomePhabricator

uabelho (Mikael Holmén)
User

Projects

User does not belong to any projects.

User Details

User Since
Dec 3 2015, 1:10 AM (226 w, 5 d)

Recent Activity

Today

uabelho created D77651: [IfConversion] Disallow TrueBB == FalseBB for valid diamonds.
Tue, Apr 7, 8:39 AM
uabelho added a comment to D77651: [IfConversion] Disallow TrueBB == FalseBB for valid diamonds.

I have no idea if this is the best fix for
https://bugs.llvm.org/show_bug.cgi?id=45302
but I saw that we've made a similar fix for triangles in 957e090ac9 and thought maybe this could be an easy way out in this case.

Tue, Apr 7, 8:39 AM
uabelho updated the summary of D77651: [IfConversion] Disallow TrueBB == FalseBB for valid diamonds.
Tue, Apr 7, 8:39 AM
uabelho added a comment to D77620: [SimpleLoopUnswitch] Do not delete DT edge when a duplicate exists..

I don't really know this code but at least the fix avoids the crash I saw. Thanks!

Tue, Apr 7, 2:40 AM · Restricted Project

Tue, Mar 31

uabelho added a comment to D77160: Fix PR45371: SeparateConstOffsetFromGEP clean up bookkeeping.

Thanks! This indeed seem to solve the problem I saw.

Tue, Mar 31, 11:58 PM · Restricted Project

Fri, Mar 27

uabelho committed rG7d482e921353: Fix TBAA for unsigned fixed-point types (authored by uabelho).
Fix TBAA for unsigned fixed-point types
Fri, Mar 27, 2:39 AM
uabelho closed D76856: Fix TBAA for unsigned fixed-point types.
Fri, Mar 27, 2:38 AM · Restricted Project

Fri, Mar 13

uabelho committed rGabc238a3c736: [libunwind] Silence warnings when __mips_hard_float is not defined (authored by uabelho).
[libunwind] Silence warnings when __mips_hard_float is not defined
Fri, Mar 13, 1:33 AM

Mar 5 2020

uabelho committed rGcd1dc7f15d63: [AST] Replace assert with llvm_unreachable to silence compiler warning (authored by uabelho).
[AST] Replace assert with llvm_unreachable to silence compiler warning
Mar 5 2020, 2:46 AM

Feb 24 2020

uabelho added a comment to D74792: [SimplifyLibCalls][IRBuilder] Accept any IRBuilder in SimplifyLibCalls.

@nikic Alright, thanks!

Feb 24 2020, 1:45 AM · Restricted Project
uabelho added a comment to D74792: [SimplifyLibCalls][IRBuilder] Accept any IRBuilder in SimplifyLibCalls.

Is this supposed to affect the output from instcombine?

Feb 24 2020, 12:42 AM · Restricted Project

Feb 21 2020

uabelho added a comment to D74901: [ms] [llvm-ml] Remove unused functions.

I have no idea if it's reasonable to remove these methods but it does indeed silence the compiler warnings about unused functions that I saw. Thanks for that.

Feb 21 2020, 12:14 AM · Restricted Project

Feb 10 2020

uabelho committed rGa50c0b0df733: Fix compiler warning when compiling without asserts [NFC] (authored by uabelho).
Fix compiler warning when compiling without asserts [NFC]
Feb 10 2020, 5:03 AM

Jan 27 2020

uabelho added inline comments to D51028: [BranchFolder] Drop kill/dead flags if they aren't present in all merged instructions.
Jan 27 2020, 2:10 AM · Restricted Project
uabelho added a comment to D51028: [BranchFolder] Drop kill/dead flags if they aren't present in all merged instructions.

I am a little curious as to how these differences in flags arise. I can understand that a kill flag can be seen as an optimization and is optional. The same would go for a dead flag. But I am not sure about an undef flag... If it is present in one case but not in the other, the two instructions do not seem equivalent, or?

So I suppose your patch makes sense to me, although I am not familiar enough to understand the undef case... Perhaps some comment on how these three cases can emerge and may be treated would be good? (at least to me :-)

Jan 27 2020, 1:37 AM · Restricted Project

Jan 16 2020

uabelho added a comment to D72734: [VectorUtils] Rework the Vector Function Database (VFDatabase)..

If you are happy with it, may I ask you to formally approve it so I can submit it? (Feel free to do a full review if you prefer to do so!)

Jan 16 2020, 2:54 AM · Restricted Project

Jan 15 2020

uabelho added a comment to D72709: [codegen,amdgpu] Enhance MIR DIE and re-arrange it for AMDGPU..

In my out-of-tree target we are running DeadMachineInstructionElim after SSA, and now of course the new assert fails.

Jan 15 2020, 11:39 PM · Restricted Project

Jan 14 2020

uabelho added a comment to D72734: [VectorUtils] Rework the Vector Function Database (VFDatabase)..

@uabelho , let me know if the introduction of isTLIScalarize prevents the regressions you have seen in your out-of-tree compiler.

Jan 14 2020, 11:58 PM · Restricted Project

Jan 13 2020

uabelho added a comment to D67572: [VectorUtils] Introduce the Vector Function Database (VFDatabase)..

Would that work for you?

Jan 13 2020, 10:43 PM · Restricted Project

Jan 8 2020

uabelho committed rG8e2b44f7e064: [Intrinsic] Add fixed point division intrinsics. (authored by ebevhan).
[Intrinsic] Add fixed point division intrinsics.
Jan 8 2020, 6:26 AM
uabelho closed D70007: [Intrinsic] Add fixed point division intrinsics..
Jan 8 2020, 6:25 AM · Restricted Project
uabelho added a comment to D70007: [Intrinsic] Add fixed point division intrinsics..

I'll submit this for @ebevhan in a little bit.

Jan 8 2020, 6:16 AM · Restricted Project

Dec 19 2019

uabelho removed a watcher for debug-info: uabelho.
Dec 19 2019, 4:59 AM
uabelho added reviewers for D51028: [BranchFolder] Drop kill/dead flags if they aren't present in all merged instructions: qcolombet, MatzeB, jonpa.
Dec 19 2019, 12:49 AM · Restricted Project

Dec 17 2019

uabelho updated the diff for D51028: [BranchFolder] Drop kill/dead flags if they aren't present in all merged instructions.

Rebased, updated to drop dead flags as well.

Dec 17 2019, 6:01 AM · Restricted Project

Dec 13 2019

uabelho added a comment to D67572: [VectorUtils] Introduce the Vector Function Database (VFDatabase)..

Ah, OK. I see what you mean. I think we could solve this by scalarizing after vectorization, instead of doing it in the vectorizer.

We could have a IR pass that runs after the vectorizer that looks for intrinsics calls .When it sees an intrinsics that operates on vector, it checks whether the target is able to lower it to some function or instruction. If not, it scalarizes it. With this we wouldn't have to introduce special behavior in the vectorizer for handling intrinsics: it could just vectorize any call to intrinsics for which vectorization make sense.

Dec 13 2019, 3:12 AM · Restricted Project
uabelho updated subscribers of D67572: [VectorUtils] Introduce the Vector Function Database (VFDatabase)..
Dec 13 2019, 12:16 AM · Restricted Project

Dec 12 2019

uabelho added a comment to D67572: [VectorUtils] Introduce the Vector Function Database (VFDatabase)..

@uabelho: would it be possible for you to provide me a minimal reproducer that I could use to craft the (wip) solution I have in mind?

Dec 12 2019, 11:28 PM · Restricted Project
uabelho added a comment to D67572: [VectorUtils] Introduce the Vector Function Database (VFDatabase)..

[...]

Is this change in behavior intended?

This change in behavior sounds a bit worrying for down-stream targets.

I think we should have at least an assertion making sure the check in LoopVEctorizationLegality succeeds in all cases it did previously with isFunctionVectorizable, otherwise down-stream targets will silently miss out on vectorization.

Dec 12 2019, 2:54 AM · Restricted Project
uabelho added a comment to D67572: [VectorUtils] Introduce the Vector Function Database (VFDatabase)..

Thanks for the reply!

Dec 12 2019, 1:57 AM · Restricted Project

Dec 11 2019

uabelho added a comment to D67572: [VectorUtils] Introduce the Vector Function Database (VFDatabase)..

A question regarding this patch.
For my out-of-tree target vectorization of intrinsics added for my target seems to have stopped working with this patch.
Is there something/what do I have to do to make the vectorizer understand my intrinsics are vectorizable?

Dec 11 2019, 6:54 AM · Restricted Project

Dec 10 2019

uabelho added a comment to D71279: [DebugInfo][MachineSink] Don't stop copy-propagating DBG_VALUEs that will have a sunk copy created.

I think you're on the right track. My mir-reproducer passes with this patch, so now I get the wanted

Dec 10 2019, 11:19 PM · Restricted Project
uabelho added a comment to D70676: [DebugInfo] Don't repeatedly created undef DBG_VALUEs during machine-sinking.

D71283 Should (TM) fix it, but, the x86 test that I wrote and which seemed to replicate the issue, now no longer replicates the issue. Which is unfortunate.

Would you be able to give that patch (and its parent) a test to see whether it fixes the problem you're encountering? Storing the subregister separately should entirely fix this I believe, I'm just having problems replicating it on x86.

Dec 10 2019, 11:19 PM · Restricted Project
uabelho added a comment to D71283: [WIP][DebugInfo][MachineSink] Preserve DBG_VALUE subregisters when sinking.

I think you're on the right track. My mir-reproducer passes with this patch, so now I get the wanted

Dec 10 2019, 11:10 PM · Restricted Project
uabelho committed rG4763267eeee7: [LegalizeTypes] Bugfixes for big-endian targets when handling BITCASTs (authored by uabelho).
[LegalizeTypes] Bugfixes for big-endian targets when handling BITCASTs
Dec 10 2019, 2:32 AM
uabelho committed rG4d280d3ac06a: Add testcases exposing PR44135 (authored by uabelho).
Add testcases exposing PR44135
Dec 10 2019, 2:32 AM
uabelho closed D70942: [LegalizeTypes] Bugfixes for big-endian targets when handling BITCASTs.
Dec 10 2019, 2:32 AM · Restricted Project
uabelho added a comment to D70942: [LegalizeTypes] Bugfixes for big-endian targets when handling BITCASTs.

The load version is a lot more instructions, so it's probably not worth it... the current patch should be fine as-is.

Dec 10 2019, 2:32 AM · Restricted Project

Dec 9 2019

uabelho updated subscribers of D70942: [LegalizeTypes] Bugfixes for big-endian targets when handling BITCASTs.

LGTM. (Left some notes on the testcase if anyone else wants to follow.)

Dec 9 2019, 6:22 AM · Restricted Project
uabelho added a comment to D70676: [DebugInfo] Don't repeatedly created undef DBG_VALUEs during machine-sinking.

Ouch, yeah, I can see exactly why that is: the sunk DBG_VALUE is copied from the old / "original" DBG_VALUE, which in the meantime has been copy-propagated. And through the copy propagation, it grows an extra piece of subregister information.

This should be straightforwards to fix, I'll have a patch up shortly, thanks for the report!

Dec 9 2019, 5:40 AM · Restricted Project
uabelho added a comment to D70676: [DebugInfo] Don't repeatedly created undef DBG_VALUEs during machine-sinking.

I've started seeing a verifier complaint with this patch.
I don't have a full testcase to share since I get this on our out-of-tree
target but maybe you can make somethng out of this anyway.

Dec 9 2019, 5:13 AM · Restricted Project

Dec 6 2019

uabelho committed rGd8821adacbb0: [clangd] Fix gcc warning about extra ";" [NFC] (authored by uabelho).
[clangd] Fix gcc warning about extra ";" [NFC]
Dec 6 2019, 2:29 AM

Dec 5 2019

uabelho added a comment to D70942: [LegalizeTypes] Bugfixes for big-endian targets when handling BITCASTs.

Thanks for the suggestion @spatel. Updated the testcase.

Dec 5 2019, 11:20 PM · Restricted Project
uabelho updated the diff for D70942: [LegalizeTypes] Bugfixes for big-endian targets when handling BITCASTs.

Added pre-commit of the testcase, changed testcase to run all the way to ASM output so we can use utils/update_llc_test_checks.py.

Dec 5 2019, 11:20 PM · Restricted Project

Dec 3 2019

uabelho added a comment to D70942: [LegalizeTypes] Bugfixes for big-endian targets when handling BITCASTs.

Originally triggered this problem for our out-of-tree target but I think it's exposed on ARM as well.

Dec 3 2019, 12:24 AM · Restricted Project
uabelho updated subscribers of D70942: [LegalizeTypes] Bugfixes for big-endian targets when handling BITCASTs.
Dec 3 2019, 12:24 AM · Restricted Project
uabelho created D70942: [LegalizeTypes] Bugfixes for big-endian targets when handling BITCASTs.
Dec 3 2019, 12:15 AM · Restricted Project

Nov 18 2019

uabelho added a comment to D70298: [LV] Avoid considering scalar-with-predication instructions as also uniform-after-vectorization, fix PR40816.

Nice! This indeed seems to solve the problem we saw in PR40816.

I don't know the code but I can at least provide some additional testing by including this patch in my weekend testing to see nothing unexpected pops up there.

Nov 18 2019, 1:03 AM · Restricted Project

Nov 15 2019

uabelho added a comment to D70298: [LV] Avoid considering scalar-with-predication instructions as also uniform-after-vectorization, fix PR40816.

Nice! This indeed seems to solve the problem we saw in PR40816.

Nov 15 2019, 7:24 AM · Restricted Project
uabelho committed rG1587c7e86f1c: [Scalarizer] Treat values from unreachable blocks as undef (authored by uabelho).
[Scalarizer] Treat values from unreachable blocks as undef
Nov 15 2019, 2:18 AM
uabelho closed D70171: [Scalarizer] Treat values from unreachable blocks as undef.
Nov 15 2019, 2:18 AM · Restricted Project

Nov 13 2019

uabelho created D70171: [Scalarizer] Treat values from unreachable blocks as undef.
Nov 13 2019, 4:34 AM · Restricted Project

Nov 12 2019

uabelho added a comment to D69935: [DeclCXX] Remove unknown external linkage specifications.

Don't you need to also remove

case LinkageSpecDecl::lang_cxx_11:
case LinkageSpecDecl::lang_cxx_14:

from VisitLinkageSpecDecl in clang-tools-extra/modularize/Modularize.cpp? (added in r372714 / e07376a320d to silence a clang warning).
I can't see how that code would compile otherwise?

+1 to this

Nov 12 2019, 3:53 AM · Restricted Project

Nov 11 2019

uabelho committed rGc8e4b536771e: [VFABI] Remove unused variables in testcase, fix buildbot (authored by uabelho).
[VFABI] Remove unused variables in testcase, fix buildbot
Nov 11 2019, 11:35 PM

Nov 8 2019

uabelho added a comment to D69935: [DeclCXX] Remove unknown external linkage specifications.

Don't you need to also remove

Nov 8 2019, 12:13 AM · Restricted Project

Oct 31 2019

uabelho committed rGc9504954052a: [MustExecute] Silence clang warning about unused captured 'this' (authored by uabelho).
[MustExecute] Silence clang warning about unused captured 'this'
Oct 31 2019, 1:53 AM

Oct 22 2019

uabelho added a comment to D69028: [DebugInfo] Correctly place DW_OP_derefs for arguments passed on stack.

I got another testcase that also started failing with the original commit that I hoped would be the same problem, but that isn't solved yet with this fix so I'll need to dig into that one and see what's going on there.

That was probably false alarm, I think it's a problem in our testcase rather than in the patch.

Oct 22 2019, 2:12 AM · Restricted Project

Oct 17 2019

uabelho added a comment to D69028: [DebugInfo] Correctly place DW_OP_derefs for arguments passed on stack.

I got another testcase that also started failing with the original commit that I hoped would be the same problem, but that isn't solved yet with this fix so I'll need to dig into that one and see what's going on there.

Oct 17 2019, 12:58 AM · Restricted Project

Oct 16 2019

uabelho added a comment to D69028: [DebugInfo] Correctly place DW_OP_derefs for arguments passed on stack.

Cool, here's a version with deref_size;

Oct 16 2019, 11:35 PM · Restricted Project
uabelho added inline comments to D69028: [DebugInfo] Correctly place DW_OP_derefs for arguments passed on stack.
Oct 16 2019, 5:30 AM · Restricted Project
uabelho added a comment to D68945: [DebugInfo] Don't translate dbg.addr and similar intrinsics into indirect DBG_VALUEs.

Hi Mikael,

And before this change we got the following after Isel:

DBG_VALUE %fixed-stack.1, 0, !"bar_y", !DIExpression(DW_OP_LLVM_convert, 16, DW_ATE_signed, DW_OP_LLVM_convert, 32, DW_ATE_signed, DW_OP_stack_value)

With this change, we instead get this after Isel:

DBG_VALUE %fixed-stack.1, $noreg, !"bar_y", !DIExpression(DW_OP_LLVM_convert, 16, DW_ATE_signed, DW_OP_LLVM_convert, 32, DW_ATE_signed, DW_OP_deref, DW_OP_stack_value)

Isn't the DW_OP_deref inserted in the wrong place? I think it should be done before the DW_OP_LLVM_convert:s rather than after?

You're right, that definitely looks wrong. This change was only supposed to affect DBG_VALUEs generated from indirect intrinsics (dbg.addr/dbg.declare); at a guess, it looks like dbg.values of Values that becomes FrameIndexes have the IsIndirect flag set too. I'll try to replicate this locally and patch it, please do back the commit out if it's causing significant misery.

Oct 16 2019, 4:06 AM · Restricted Project
uabelho added a comment to D68945: [DebugInfo] Don't translate dbg.addr and similar intrinsics into indirect DBG_VALUEs.

I'm struggling with a case for my out-of-tree target where I think debug info is wrong with this change.

Oct 16 2019, 2:55 AM · Restricted Project

Oct 7 2019

uabelho added a comment to D68460: [MachineSink] Don't preserve MachineLoopInfo.

Would it be possible to add a verifyAnalysis function to MLI and check if a freshly calculated one matches the 'preserved' one?

Oct 7 2019, 12:47 AM · Restricted Project

Oct 6 2019

uabelho added a comment to D67968: [TableGen] Introduce a generic automaton (DFA) backend.

clang-cuda-build buildbot failed too:
http://lab.llvm.org:8011/builders/clang-cuda-build/builds/37865/steps/ninja%20check%201/logs/stdio

Oct 6 2019, 11:47 PM · Restricted Project

Oct 4 2019

uabelho added a comment to D68460: [MachineSink] Don't preserve MachineLoopInfo.

Does this make sense?

Oct 4 2019, 5:42 AM · Restricted Project
uabelho created D68460: [MachineSink] Don't preserve MachineLoopInfo.
Oct 4 2019, 5:42 AM · Restricted Project

Oct 2 2019

uabelho added inline comments to D68235: [Dominators][CodeGen] Add MachinePostDominatorTree verification.
Oct 2 2019, 7:01 AM · Restricted Project
uabelho added inline comments to D68235: [Dominators][CodeGen] Add MachinePostDominatorTree verification.
Oct 2 2019, 1:35 AM · Restricted Project

Sep 25 2019

uabelho committed rG43fd14caa060: [SortIncludesTest] Add SortPriority fields to fix -Wmissing-field-initializers… (authored by uabelho).
[SortIncludesTest] Add SortPriority fields to fix -Wmissing-field-initializers…
Sep 25 2019, 11:49 PM
uabelho committed rL372944: [SortIncludesTest] Add SortPriority fields to fix -Wmissing-field-initializers….
[SortIncludesTest] Add SortPriority fields to fix -Wmissing-field-initializers…
Sep 25 2019, 11:49 PM
uabelho committed rG957e090ac958: [IfConversion] Disallow TBB == FBB for valid triangles (authored by uabelho).
[IfConversion] Disallow TBB == FBB for valid triangles
Sep 25 2019, 11:43 PM
uabelho added a comment to D67832: [IfConversion] Disallow TBB == FBB for valid triangles.

LGTM

Sep 25 2019, 11:43 PM · Restricted Project
uabelho committed rL372943: [IfConversion] Disallow TBB == FBB for valid triangles.
[IfConversion] Disallow TBB == FBB for valid triangles
Sep 25 2019, 11:34 PM
uabelho closed D67832: [IfConversion] Disallow TBB == FBB for valid triangles.
Sep 25 2019, 11:34 PM · Restricted Project
uabelho added a comment to D67832: [IfConversion] Disallow TBB == FBB for valid triangles.

Would it make more sense to just say this isn't a triangle? We don't really want to do loop peeling in IfConversion.

Sep 25 2019, 4:43 AM · Restricted Project
uabelho updated the diff for D67832: [IfConversion] Disallow TBB == FBB for valid triangles.

Disallow this case in ValidTriangle instead.

Sep 25 2019, 4:42 AM · Restricted Project

Sep 24 2019

uabelho committed rL372748: Request commit access for uabelho.
Request commit access for uabelho
Sep 24 2019, 6:04 AM
uabelho added a comment to D67613: [DWARF-5] Support for DWARF-5 C++ language tags.

/srv/llvm-buildbot-srcatch/llvm-build-dir/clang-x86_64-debian-fast/llvm.src/tools/clang/tools/extra/modularize/Modularize.cpp:583:13: warning: enumeration values 'lang_cxx_11' and 'lang_cxx_14' not handled in switch [-Wswitch]
1 warning generated.

We also get that warning when compiling with clang 8:

../../clang-tools-extra/modularize/Modularize.cpp:583:13: error: enumeration values 'lang_cxx_11' and 'lang_cxx_14' not handled in switch [-Werror,-Wswitch]
    switch (D->getLanguage()) {
            ^
1 error generated.
Sep 24 2019, 2:46 AM · Restricted Project, Restricted Project, debug-info
uabelho committed rGe07376a320db: [modularize] Fix compilation warning after r372681 (authored by uabelho).
[modularize] Fix compilation warning after r372681
Sep 24 2019, 2:44 AM
uabelho committed rL372714: [modularize] Fix compilation warning after r372681.
[modularize] Fix compilation warning after r372681
Sep 24 2019, 2:44 AM

Sep 23 2019

uabelho added a comment to D67613: [DWARF-5] Support for DWARF-5 C++ language tags.

/srv/llvm-buildbot-srcatch/llvm-build-dir/clang-x86_64-debian-fast/llvm.src/tools/clang/tools/extra/modularize/Modularize.cpp:583:13: warning: enumeration values 'lang_cxx_11' and 'lang_cxx_14' not handled in switch [-Wswitch]
1 warning generated.

Sep 23 2019, 11:25 PM · Restricted Project, Restricted Project, debug-info

Sep 20 2019

uabelho created D67832: [IfConversion] Disallow TBB == FBB for valid triangles.
Sep 20 2019, 6:44 AM · Restricted Project
uabelho added a comment to D67764: [LV] Forced vectorization with runtime checks and OptForSize.

It fixes the problem I reported. Thanks!

Sep 20 2019, 2:54 AM · Restricted Project

Sep 11 2019

uabelho added a comment to D67417: [LICM/AST] Check if the AliasAny set is removed from the tracker..

I've no idea if the fix itself makes sense but at least it does seem to fix my reproducer for PR38513 and I didn't see any problems with the patch during the (limited) testing I've done.

Sep 11 2019, 12:39 AM · Restricted Project

Sep 10 2019

uabelho added a comment to D67171: LLVM_COMPILE_FLAGS also applies to C files.

Hi @uabelho – Try r371521

Sep 10 2019, 11:25 PM · Restricted Project
uabelho added a comment to D67171: LLVM_COMPILE_FLAGS also applies to C files.

When compiling with gcc, we get warnings with this commit:

[100/4153] Building C object lib/Support/CMakeFiles/LLVMSupport.dir/regfree.c.o
cc1: warning: command line option '-fno-rtti' is valid for C++/ObjC++ but not for C
[101/4153] Building C object lib/Support/CMakeFiles/LLVMSupport.dir/regstrlcpy.c.o
cc1: warning: command line option '-fno-rtti' is valid for C++/ObjC++ but not for C
[102/4153] Building C object lib/Support/CMakeFiles/LLVMSupport.dir/regerror.c.o
cc1: warning: command line option '-fno-rtti' is valid for C++/ObjC++ but not for C
[107/4153] Building C object lib/Support/CMakeFiles/LLVMSupport.dir/regexec.c.o
cc1: warning: command line option '-fno-rtti' is valid for C++/ObjC++ but not for C
[114/4153] Building C object lib/Support/CMakeFiles/LLVMSupport.dir/regcomp.c.o
cc1: warning: command line option '-fno-rtti' is valid for C++/ObjC++ but not for C
Sep 10 2019, 6:15 AM · Restricted Project

Sep 6 2019

uabelho added a comment to D67209: [MIR] MIR Namer pass.

I did a minor change to the test case in r371171 since the

;CHECK: bb

checks matched on the line

;ModuleID = '/repo/bb/

in the output instead of the wanted "bb.0:".

Sep 6 2019, 12:02 AM · Restricted Project
uabelho committed rGdee0702b2a9d: [MIR] Change test case to read from stdin instead of file (authored by uabelho).
[MIR] Change test case to read from stdin instead of file
Sep 6 2019, 12:00 AM
uabelho committed rL371171: [MIR] Change test case to read from stdin instead of file.
[MIR] Change test case to read from stdin instead of file
Sep 6 2019, 12:00 AM

Sep 4 2019

uabelho added a comment to D66803: [LV] Tail-folding with runtime memory checks.

Normally we do use basicaa, the crash was found in "fuzz" tests where we compile the code with random flags.

Sep 4 2019, 7:00 AM · Restricted Project
uabelho added a comment to D66803: [LV] Tail-folding with runtime memory checks.

Why would it be ok to give the assert when we run

Sep 4 2019, 5:29 AM · Restricted Project
uabelho added a comment to D66803: [LV] Tail-folding with runtime memory checks.

Hi,

I've hit the new assertion when compiling for my out of tree target when using -Osize in combination with

#pragma clang loop vectorize(enable)

on a loop.

What is supposed to prevent us from triggering the assertion in a case like that?

Sep 4 2019, 3:49 AM · Restricted Project
uabelho added a comment to D66803: [LV] Tail-folding with runtime memory checks.

I've hit the new assertion when compiling for my out of tree target when using -Osize in combination with

Sep 4 2019, 1:00 AM · Restricted Project

Aug 16 2019

uabelho added inline comments to D65683: MVT: Add v3i16/v3f16 vectors.
Aug 16 2019, 12:38 AM

Jul 11 2019

uabelho committed rG7618b2a5c2af: [test] Silence gcc 7.4 warning [NFC] (authored by uabelho).
[test] Silence gcc 7.4 warning [NFC]
Jul 11 2019, 12:08 AM
uabelho committed rL365738: [test] Silence gcc 7.4 warning [NFC].
[test] Silence gcc 7.4 warning [NFC]
Jul 11 2019, 12:07 AM

Jul 10 2019

uabelho committed rGc593f5e6711a: [clang-doc] Silence compiler warning with gcc 7.4 [NFC] (authored by uabelho).
[clang-doc] Silence compiler warning with gcc 7.4 [NFC]
Jul 10 2019, 11:51 PM
uabelho committed rL365736: [clang-doc] Silence compiler warning with gcc 7.4 [NFC].
[clang-doc] Silence compiler warning with gcc 7.4 [NFC]
Jul 10 2019, 11:51 PM

Jul 9 2019

uabelho committed rG77392c3f5e79: Silence gcc warning by adding parentheses to condition [NFC] (authored by uabelho).
Silence gcc warning by adding parentheses to condition [NFC]
Jul 9 2019, 11:20 PM
uabelho committed rL365597: Silence gcc warning by adding parentheses to condition [NFC].
Silence gcc warning by adding parentheses to condition [NFC]
Jul 9 2019, 11:20 PM