Displaying 20 results from an estimated 300 matches similar to: "Bug in TableGen RegisterBankEmitter"
2017 May 10
2
Bug in TableGen RegisterBankEmitter
Hi Tom,
The output:
Added VReg_64(explicit)
Added VS_32(explicit (VS_32) VReg_64 class-with-subregs: VReg_64)
is saying that VS_32 was added because VReg_64 was explicitly specified and that while inspecting VS_32, it noticed that every register in VS_32 was a subregister of a register from VReg_64 using a single common subregister index.
I've added some more tracing to my local copy and
2017 May 16
2
Bug in TableGen RegisterBankEmitter
On 05/16/2017 11:57 AM, Daniel Sanders wrote:
>> If that's right, one possible fix would be to rename some of the subregister indices but that's likely to be quite painful. I'll have a think and see if I can come up with something nicer.
>
> I haven't been able to come up with a better answer for this, just an alternate choice as to where the complexity is. If we were
2020 Nov 19
1
Problems with undef subranges in identity copies
Hi,
I'm stuck trying to fix a variety of problems that occur with undef
subregisters when the register coalescer eliminates identity
copies. The fundamental problem is complexity from the fact that undef
values are a special case since they don't have an associated
VNInfo/Segment unless the value is used across blocks.
For example, in this case, %0 has 2 subregisters sub0 and sub1:
2019 Sep 09
2
Fwd: MachineScheduler not scheduling for latency
Hi,
I'm trying to understand why MachineScheduler does a poor job in
straight line code in cases like the one in the attached debug dump.
This is on AMDGPU, an in-order target, and the problem is that the
IMAGE_SAMPLE instructions have very high (80 cycle) latency, but in
the resulting schedule they are often placed right next to their uses
like this:
1784B %140:vgpr_32 =
2016 Mar 28
0
RFC: atomic operations on SI+
On Fri, Mar 25, 2016 at 02:22:11PM -0400, Jan Vesely wrote:
> Hi Tom, Matt,
>
> I'm working on a project that needs few coherent atomic operations (HSA
> mode: load, store, compare-and-swap) for std::atomic_uint in HCC.
>
> the attached patch implements atomic compare and swap for SI+
> (untested). I tried to stay within what was available, but there are
> few issues
2015 Mar 27
2
[LLVMdev] Question about load clustering in the machine scheduler
On Thu, Mar 26, 2015 at 11:50:20PM -0700, Andrew Trick wrote:
>
> > On Mar 26, 2015, at 7:36 PM, Tom Stellard <tom at stellard.net> wrote:
> >
> > Hi,
> >
> > I have a program with over 100 loads (each with a 10 cycle latency)
> > at the beginning of the program, and I can't figure out how to get
> > the machine scheduler to intermix ALU
2019 Sep 10
2
MachineScheduler not scheduling for latency
Hi Andy,
Thanks for the explanations. Yes AMDGPU is in-order and has
MicroOpBufferSize = 1.
Re "issue limited" and instruction groups: could it make sense to
disable the generic scheduler's detection of issue limitation on
in-order CPUs, or on CPUs that don't define instruction groups, or
some similar condition? Something like:
--- a/lib/CodeGen/MachineScheduler.cpp
+++
2016 Mar 25
2
RFC: atomic operations on SI+
Hi Tom, Matt,
I'm working on a project that needs few coherent atomic operations (HSA
mode: load, store, compare-and-swap) for std::atomic_uint in HCC.
the attached patch implements atomic compare and swap for SI+
(untested). I tried to stay within what was available, but there are
few issues that I was unsure how to address:
1.) it currently uses v2i32 for both input and output. This
2017 Oct 14
3
darwin bootstrap failure
On Sat, Oct 14, 2017 at 10:25 AM, Don Hinton <hintonda at gmail.com> wrote:
> Hi Jack:
>
> Looks like I missed this one in my recent change.
>
> Please let me know if this solves your problem:
>
> $ git diff
> diff --git a/utils/TableGen/InfoByHwMode.cpp
> b/utils/TableGen/InfoByHwMode.cpp
> index 7e1e1864356..8d3636432aa 100644
> ---
2017 Jan 21
12
[GlobalISel] Quick Status
Hi all,
Following the thread from http://lists.llvm.org/pipermail/llvm-dev/2017-January/109029.html, I am sending this email to give a status on GlobalISel progress and situation.
We are pushing GlobalISel from the state of prototype to a production quality framework. We welcome help with patches, reviews, feedbacks and so on.
As explained during the last developer meeting, we are aiming at
2017 Oct 14
2
darwin bootstrap failure
Is anyone else seeing this bootstrap failure on current svn trunk?
[ 6%] Linking CXX executable ../../bin/llvm-tblgen
cd /sw/src/fink.build/llvm60-6.0.0-1/build/stage1/utils/TableGen &&
/sw/bin/cmake -E cmake_link_script CMakeFiles/llvm-tblgen.dir/link.txt
--verbose=1
/sw/src/fink.build/llvm60-6.0.0-1/opt-bin/ccclang++ -fno-common -fPIC
-fvisibility-inlines-hidden -Werror=date-time
2017 Oct 14
2
darwin bootstrap failure
On Sat, Oct 14, 2017 at 11:25 AM, Don Hinton <hintonda at gmail.com> wrote:
> Hi Jack:
>
> Yes, I was just looking at that. Seems like TableGen wasn't done along
> with the rest of llvm. I'll work up a complete patch shortly.
>
> Btw, I'm curious how this happened. Do you have a stale CMakeCache.txt by
> any chance? You might check the value for
2017 Oct 15
2
darwin bootstrap failure
On Sat, Oct 14, 2017 at 11:25 AM, Don Hinton via llvm-dev
<llvm-dev at lists.llvm.org> wrote:
> Hi Jack:
>
> Yes, I was just looking at that. Seems like TableGen wasn't done along with
> the rest of llvm. I'll work up a complete patch shortly.
This also broke the build for MSVC when doing a debug build (though no
builder seems to be picking up the failure!). After
2019 Jan 23
2
Windows/Clang build instrumented/PGO
Hello LLVM developers,
Following some hints on this mailing list earlier this year on how to make
clang faster than stock llvm.org builds I have implemented a script that
builds a PGO optimized version of clang by following the guide here:
http://llvm.org/docs/HowToBuildWithPGO.html
This works great on macOS and Linux - we gained almost 15% in our project
with this technique. I am now looking at
2017 Oct 15
2
darwin bootstrap failure
On Sun, Oct 15, 2017 at 10:58 AM, Don Hinton <hintonda at gmail.com> wrote:
> Thanks Aaron.
>
> I don't have a Windows system, and haven't seen any buildbot failures, so I
> it's difficult to come up with a patch for something I can't reproduce
> locally or see any actual failures. Could you send me the commands you used
> that uncovered the failure?
This
2017 Oct 14
2
darwin bootstrap failure
On Sat, Oct 14, 2017 at 11:38 AM, Don Hinton <hintonda at gmail.com> wrote:
> Sorry, LLVM_FORCE_ENABLE_DUMP is the variable, which is used along with
> LLVM_ENABLE_ASSERTIONS to set LLVM_ENABLE_DUMP.
>
> Again, I'm working on a fix, but could you also provide your cmake
> command? Looks like we aren't handling your use case correctly.
>
> thanks..
> don
>
2018 Jan 13
0
Options for custom CCState, CCAssignFn, and GlobalISel
Hi LLVM developers,
Don't be quiet :) we need your suggestions for supporting custom
CCState, CCAssignFn in D41700.
And also RegisterBank in D41653. because it needs to consider about how
to support variable-sized register classes concept implemented in D24631.
And I think you might have same question when porting to GlobalISel for
your Targets, so please give us some directions, thanks
2017 Oct 15
2
darwin bootstrap failure
On Sun, Oct 15, 2017 at 11:19 AM, Don Hinton <hintonda at gmail.com> wrote:
> On Sun, Oct 15, 2017 at 8:06 AM, Aaron Ballman <aaron at aaronballman.com>
> wrote:
>>
>> On Sun, Oct 15, 2017 at 10:58 AM, Don Hinton <hintonda at gmail.com> wrote:
>> > Thanks Aaron.
>> >
>> > I don't have a Windows system, and haven't seen any
2017 Oct 14
2
darwin bootstrap failure
On Sat, Oct 14, 2017 at 4:22 PM, Don Hinton <hintonda at gmail.com> wrote:
> Hi Jack:
>
> The only way I could reproduce the problem you are seeing was to rerun
> cmake with -DCMAKE_BUILD_TYPE=Debug in a build directory previously
> configured with -DCMAKE_BUILD_TYPE=Release. I can fix that, but not sure
> if it's what you are seeing.
>
> If this isn't your
2015 Dec 02
2
fuzzer crash (but not the good kind)
Kostya,
I think I've found what looks like a reproducible bug in libFuzzer. The
code under test is built with ASan and the first ASan CHECK failure shows
fuzzer in the stack trace. (see below)
One of the factors that may be unique in my testing is that each iteration
can take a very long time to execute (tens or hundreds of seconds).
Let me know if you need more info, I think it