Page MenuHomePhabricator

madhur13490 (Madhur Amilkanthwar)
User

Projects

User does not belong to any projects.

User Details

User Since
Oct 1 2014, 1:26 AM (312 w, 2 d)

madhur13490@gmail.com, Madhur.Amilkanthwar@amd.com

Recent Activity

Today

madhur13490 added a comment to D86203: [GlobalISel][TableGen] Add handling of unannotated dst pattern ops.

Is this still planned to be checked-in?

Fri, Sep 25, 2:15 AM · Restricted Project

Wed, Sep 23

madhur13490 added a comment to D87674: [AMDGPU] Insert waitcnt after returning from call.

The revert also highlights the problem that we don't have representative test in llvm/test :(

Wed, Sep 23, 10:13 AM · Restricted Project
madhur13490 added a comment to D87674: [AMDGPU] Insert waitcnt after returning from call.

Yes, this commit is incorrect. It completely breaks code linking in Mesa OpenGL. s_waitcnt is required at the end of all global functions that return values.

Please revert. @nhaehnle

I don't understand why would it fail. This patch just moves s_waitcnt to the caller so they would be executed anyway. I think I am missing something. It would be helpful to root cause if we can isolate to a small test case.

Shader returns aren't real returns and the "caller" doesn't wait

Wed, Sep 23, 9:53 AM · Restricted Project
madhur13490 added a comment to D87674: [AMDGPU] Insert waitcnt after returning from call.

Yes, this commit is incorrect. It completely breaks code linking in Mesa OpenGL. s_waitcnt is required at the end of all global functions that return values.

Please revert. @nhaehnle

Wed, Sep 23, 9:49 AM · Restricted Project

Tue, Sep 22

madhur13490 accepted D87393: Enhance TableGen error message capabilities.

A lot of clang-format errors still exists. Looks okay otherwise.

Tue, Sep 22, 10:40 PM · Restricted Project

Sat, Sep 19

madhur13490 added a comment to D87967: TableGen: Change comments about superclass order.
Sat, Sep 19, 10:04 AM · Restricted Project

Wed, Sep 16

madhur13490 accepted D87674: [AMDGPU] Insert waitcnt after returning from call.
Wed, Sep 16, 7:29 AM · Restricted Project

Tue, Sep 15

madhur13490 added a comment to D87674: [AMDGPU] Insert waitcnt after returning from call.
Tue, Sep 15, 10:04 AM · Restricted Project
madhur13490 added inline comments to D87674: [AMDGPU] Insert waitcnt after returning from call.
Tue, Sep 15, 8:44 AM · Restricted Project

Mon, Sep 14

madhur13490 added a comment to D87393: Enhance TableGen error message capabilities.

@madhur13490 I simply copied the preceding setValue() function. Let me commit this the way it is and then I will revisit both functions.

I will capitalize the induction variable.

Mon, Sep 14, 6:59 AM · Restricted Project
madhur13490 added inline comments to D87393: Enhance TableGen error message capabilities.
Mon, Sep 14, 5:36 AM · Restricted Project

Tue, Sep 8

madhur13490 added inline comments to D87000: Add a new hidden option -print-changes that reports in a patch-like notation when a pass actually changes the IR..
Tue, Sep 8, 2:05 AM · Restricted Project
madhur13490 added inline comments to D87202: Add a new hidden option -dot-cfg-changes which creates a website of DOT files showing colourized changes as the IR is changed by passes in the new pass manager pipeline..
Tue, Sep 8, 1:43 AM · Restricted Project

Sun, Aug 30

madhur13490 added a comment to D86362: Allow graph writer to render DOT nodes using HTML..

I can't access the link in the description of the change. Moreover, I don't understand the purpose of making several calls to DTraits.renderNodeUsingHTML(Node). In its current form, the code queries just once and uses the value throughout the code, with your change you'd be calling several times. If this is a pre-requisite to some other change then I'd like to see that change so understand the whole picture. (Phabricator allows you to link revisions and even create a dependency FWIW.)

Sun, Aug 30, 2:10 AM · Restricted Project
madhur13490 added inline comments to D86836: Support a list of CostPerUse values.
Sun, Aug 30, 1:49 AM · Restricted Project
madhur13490 updated subscribers of D86362: Allow graph writer to render DOT nodes using HTML..

Reviewing. Sorry for the delay, need a day or so.

Sun, Aug 30, 12:25 AM · Restricted Project

Aug 22 2020

madhur13490 updated madhur13490.
Aug 22 2020, 1:47 AM
madhur13490 added a comment to D86203: [GlobalISel][TableGen] Add handling of unannotated dst pattern ops.

What happens if the instruction operand uses an unallocatable pseudo-class combining register classes with different banks? I would expect it would need to check any of the bank possibilities

Hm, not sure what you mean. Could you provide a brief example?

The most common AMDGPU instructions define VS_* pseudoclasses for operand constraints. The two classes added have different register banks, since the instructions support directly reading from either.
e.g.
RegisterClass VS_32 = {VGPR_32RegClass, SGPR_32RegClass}, where both of these register classes are different banks.

In terms of selecting a particular operand, there's an additional hazard. We can't freely use SGPR_32 in a given operand without considering the context of the other operands. We avoid solving this in GlobalISel by always assigning these operands to VGPRRegBankID, and relying on a later pass to optimize out these copies. We're sorely missing a RegBank legality verifier check, so I'm not sure I would want the generated patterns to infer either bank is OK.

The operands of these VS_* instructions, are the defined (in the instruction) to use the VS_32 class, or VGPR_32/SGPR_32 classes? If it is the former, then what this patch would do is to use VS_32 in the patterns. If the patterns should really be using VGPR_32/SGPR_32, then this is a problem. However, you still have the option of annotating the pattern operands just as before, so this patch would not interfere with any patterns that today are accepted by TableGen. If it is the latter, then this patch would use whatever class (VGPR_32 or SGPR_32) that is specified for the corresponding operands in the instruction, so here I don't see there being any problem.

Perhaps we could add an option that this feature is disabled by default, and by activating it you take responsibility to ensure that you don't have these kinds of situations for your target?

When a register class is an union of two or more classes then such problems bound to occur for one or more targets. Why not do such inference when it is obvious i.e. register class in instruction definition is a leaf register class and NOT an union of some base other base classes. I think this is better than having an runtime option to enable/disable the inference.
I think leaf classes can be detected programmatically.

I like that idea, and this is only applied on leaf nodes to begin with.

Aug 22 2020, 12:25 AM · Restricted Project

Aug 21 2020

madhur13490 added a comment to D86203: [GlobalISel][TableGen] Add handling of unannotated dst pattern ops.

What happens if the instruction operand uses an unallocatable pseudo-class combining register classes with different banks? I would expect it would need to check any of the bank possibilities

Hm, not sure what you mean. Could you provide a brief example?

The most common AMDGPU instructions define VS_* pseudoclasses for operand constraints. The two classes added have different register banks, since the instructions support directly reading from either.
e.g.
RegisterClass VS_32 = {VGPR_32RegClass, SGPR_32RegClass}, where both of these register classes are different banks.

In terms of selecting a particular operand, there's an additional hazard. We can't freely use SGPR_32 in a given operand without considering the context of the other operands. We avoid solving this in GlobalISel by always assigning these operands to VGPRRegBankID, and relying on a later pass to optimize out these copies. We're sorely missing a RegBank legality verifier check, so I'm not sure I would want the generated patterns to infer either bank is OK.

The operands of these VS_* instructions, are the defined (in the instruction) to use the VS_32 class, or VGPR_32/SGPR_32 classes? If it is the former, then what this patch would do is to use VS_32 in the patterns. If the patterns should really be using VGPR_32/SGPR_32, then this is a problem. However, you still have the option of annotating the pattern operands just as before, so this patch would not interfere with any patterns that today are accepted by TableGen. If it is the latter, then this patch would use whatever class (VGPR_32 or SGPR_32) that is specified for the corresponding operands in the instruction, so here I don't see there being any problem.

Perhaps we could add an option that this feature is disabled by default, and by activating it you take responsibility to ensure that you don't have these kinds of situations for your target?

Aug 21 2020, 4:31 AM · Restricted Project

Aug 19 2020

madhur13490 committed rG0313c540c2c7: [NFC] Fix typo in AMDGPU doc (authored by madhur13490).
[NFC] Fix typo in AMDGPU doc
Aug 19 2020, 7:34 AM
madhur13490 closed D86206: [NFC] Fix typo in AMDGPU doc.
Aug 19 2020, 7:33 AM · Restricted Project
madhur13490 added reviewers for D86206: [NFC] Fix typo in AMDGPU doc: t-tye, arsenm.
Aug 19 2020, 4:24 AM · Restricted Project
madhur13490 requested review of D86206: [NFC] Fix typo in AMDGPU doc.
Aug 19 2020, 4:19 AM · Restricted Project
madhur13490 committed rG8351e80cd17b: [GlobalISel] Don't skip adding predicate matcher (authored by madhur13490).
[GlobalISel] Don't skip adding predicate matcher
Aug 19 2020, 12:54 AM
madhur13490 closed D83034: [GlobalISel] Don't skip adding predicate matcher.
Aug 19 2020, 12:54 AM · Restricted Project

Aug 18 2020

madhur13490 added a comment to D83034: [GlobalISel] Don't skip adding predicate matcher.

LGTM. I think this is only a half solution, and it's still a problem that multiple builtin predicates will be silently ignored

Aug 18 2020, 10:48 PM · Restricted Project
madhur13490 updated the diff for D83034: [GlobalISel] Don't skip adding predicate matcher.

fix unexpected tabs

Aug 18 2020, 8:45 AM · Restricted Project
madhur13490 updated the diff for D83034: [GlobalISel] Don't skip adding predicate matcher.

fix formatting

Aug 18 2020, 8:43 AM · Restricted Project
madhur13490 updated the diff for D83034: [GlobalISel] Don't skip adding predicate matcher.

rebase + address comments

Aug 18 2020, 8:38 AM · Restricted Project
madhur13490 added inline comments to D83034: [GlobalISel] Don't skip adding predicate matcher.
Aug 18 2020, 8:38 AM · Restricted Project

Aug 13 2020

madhur13490 awarded D85838: New TableGen Programmer's Reference document a Like token.
Aug 13 2020, 7:36 PM · Restricted Project
madhur13490 added inline comments to D85838: New TableGen Programmer's Reference document.
Aug 13 2020, 7:18 PM · Restricted Project

Aug 11 2020

madhur13490 added a comment to D83034: [GlobalISel] Don't skip adding predicate matcher.

@arsenm , Can you please take over? I think @dsanders is on vacation.

Aug 11 2020, 9:26 AM · Restricted Project

Aug 6 2020

madhur13490 accepted D84644: AMDGPU/GlobalISel: Handle llvm.amdgcn.ds.{fadd|fmin|fmax}.
Aug 6 2020, 7:45 AM · Restricted Project

Aug 5 2020

madhur13490 added inline comments to D84644: AMDGPU/GlobalISel: Handle llvm.amdgcn.ds.{fadd|fmin|fmax}.
Aug 5 2020, 10:20 PM · Restricted Project
madhur13490 added a comment to D84644: AMDGPU/GlobalISel: Handle llvm.amdgcn.ds.{fadd|fmin|fmax}.

reviewing.

Aug 5 2020, 10:38 AM · Restricted Project

Jul 27 2020

madhur13490 added inline comments to D83034: [GlobalISel] Don't skip adding predicate matcher.
Jul 27 2020, 8:56 AM · Restricted Project

Jul 26 2020

madhur13490 updated the diff for D83034: [GlobalISel] Don't skip adding predicate matcher.

rebase + address comments

Jul 26 2020, 9:47 AM · Restricted Project

Jul 24 2020

madhur13490 added a comment to D84391: [AMDGPU] Fix incorrect arch assert while setting up FlatScratchInit.

Can we just add a predicate for whatever necessitates the SETREG for gfx10+? No idea on a good name, but if it were flatScratchIsHwreg() and it implied flatScratchIsPointer() this becomes:

if (ST.flatScratchIsHwreg()) {
  // pointer add then S_SETREG
} else if (ST.flatScratchIsPointer()) (
  // pointer add
} else {
  // size and offset dance
}
llvm_unreachable();

I agree that the existing assert here doesn't really mean anything, not sure why I wrote it.

Rather, the llvm_unreachable isn't needed if we consider the offset/add case as the "default", but maybe we should predicate it too? It would be nice if we could do this all in a way that was statically known to cover all the targets we have.

Could we combine the various predicate functions into one which returns an enumeration instead? Similar to Madhur's proposal, but without the direct reference to GFX#? I.e.

switch (ST.getFlatScratchSetupKind()) {
AMDGPU::PointerInHwreg:
  // ...
  break;
AMDGPU::PointerInSGPR:
  // ...
  break;
AMDGPU::SizeAndOffsetInSGPR:
  // ...
  break;
}

Then when we add a new variant the compiler points us to everywhere that cares.

Jul 24 2020, 11:20 AM · Restricted Project
madhur13490 committed rG4a577c3a22c4: [AMDGPU] Fix incorrect arch assert while setting up FlatScratchInit (authored by madhur13490).
[AMDGPU] Fix incorrect arch assert while setting up FlatScratchInit
Jul 24 2020, 11:19 AM
madhur13490 closed D84391: [AMDGPU] Fix incorrect arch assert while setting up FlatScratchInit.
Jul 24 2020, 11:19 AM · Restricted Project
madhur13490 updated the diff for D84391: [AMDGPU] Fix incorrect arch assert while setting up FlatScratchInit.

rebase

Jul 24 2020, 11:18 AM · Restricted Project

Jul 23 2020

madhur13490 added a reviewer for D84391: [AMDGPU] Fix incorrect arch assert while setting up FlatScratchInit: scott.linder.
Jul 23 2020, 8:55 AM · Restricted Project
madhur13490 added a comment to D84391: [AMDGPU] Fix incorrect arch assert while setting up FlatScratchInit.

I am not sure what does that mean. Do you agree with my way of refactoring or you're suggesting something else? With my approach there won't be any checks as I said we can get rid of flatScratchIsPointer() too.

I mean exactly the opposite. We should not check the generation anywhere. The hardware does not make changes in a nice, disciplined, sequenced way. Everything should be based on specific feature checks. I.e. there should only be flatScratchIsPointer checks, and nothing checking getGeneration

Jul 23 2020, 8:40 AM · Restricted Project
madhur13490 added a comment to D84391: [AMDGPU] Fix incorrect arch assert while setting up FlatScratchInit.

Needs test. Also not sure why we would have an assert for this here in the first place

In fact I like the assert. It guarantees that we're not building something insane. Moreover, should we refactor this code to something more readble? :

switch(llvm::AMDGPUSubTarget) {
case GFX:8 {}
case GFX:9: {}
...
}

Only caveat is the usage of function flatScratchIsPointer(). We can get rid of its usage in its current form but in future we may want to add some code to it to take contextual decisions.

I would like to purge all checks of the generation. The relevant bit is flatScratchIsPointer. The generation is redundant and potentially misleading.

Jul 23 2020, 7:59 AM · Restricted Project
madhur13490 added a comment to D84391: [AMDGPU] Fix incorrect arch assert while setting up FlatScratchInit.

Needs test. Also not sure why we would have an assert for this here in the first place

Jul 23 2020, 7:07 AM · Restricted Project
Herald added a project to D84391: [AMDGPU] Fix incorrect arch assert while setting up FlatScratchInit: Restricted Project.
Jul 23 2020, 2:53 AM · Restricted Project
madhur13490 accepted D84367: AMDGPU: Fix failures from overflowing uint8_t number of operands.

LGTM

Jul 23 2020, 1:21 AM · Restricted Project

Jul 21 2020

madhur13490 added inline comments to D83034: [GlobalISel] Don't skip adding predicate matcher.
Jul 21 2020, 7:12 AM · Restricted Project

Jul 20 2020

madhur13490 added inline comments to D83988: AMDGPU/GlobalISel: Start trying to handle AGPR bank.
Jul 20 2020, 8:09 AM · Restricted Project
madhur13490 added inline comments to D83988: AMDGPU/GlobalISel: Start trying to handle AGPR bank.
Jul 20 2020, 1:23 AM · Restricted Project

Jul 16 2020

madhur13490 added inline comments to D83034: [GlobalISel] Don't skip adding predicate matcher.
Jul 16 2020, 1:49 AM · Restricted Project

Jul 15 2020

madhur13490 added inline comments to D83710: TableGen/GlobalISel: Allow output instructions with multiple defs.
Jul 15 2020, 12:14 PM · Restricted Project
madhur13490 added inline comments to D83710: TableGen/GlobalISel: Allow output instructions with multiple defs.
Jul 15 2020, 12:26 AM · Restricted Project

Jul 13 2020

madhur13490 added a comment to D83034: [GlobalISel] Don't skip adding predicate matcher.

I would expect the existing tablegen tests to break from this and need updating?

Jul 13 2020, 9:25 AM · Restricted Project
madhur13490 updated the diff for D83034: [GlobalISel] Don't skip adding predicate matcher.

rebase + add test

Jul 13 2020, 9:15 AM · Restricted Project
madhur13490 added a comment to D83034: [GlobalISel] Don't skip adding predicate matcher.

Could you add a test case or point us at a example of an existing test that goes wrong? The description in the commit message is unlikely to be the full story as we already cover loads with non-null MemoryVT's. My best guess is you are attempting to use builtin predicates and custom predicates together. I don't see a reason why that shouldn't be allowed but it's not something that was intended as the goal was aiming to fully remove the custom C++ from the tablegen headers so that tablegen could do some transformations on sextload/zextload and similar to fix DAGISel vs GlobalISel modelling mismatches.

I think the problem is broader than just combining custom predicates and builtin. The emitter here implicitly assumes all of these builtin PatFrag predicates are used exactly as the hierarchy used to define the default/generic load/store patterns. However, the PatFrags are much more free form and you can define a patfrag that combines multiple of these predicates in the same "layer" of the load/store hierarchy. The AMDGPU patterns redefine the entire set of load/store patterns, and in some cases it makes sense to combine all the predicates at once. I had to somewhat artificially add new layers of PatFrags to only apply a single predicate at a time. This also isn't consistently applied (for example, it does work to combine the AddressSpaces predicate and alignment)

Jul 13 2020, 9:13 AM · Restricted Project

Jul 6 2020

madhur13490 updated subscribers of D83034: [GlobalISel] Don't skip adding predicate matcher.

Ping!

Jul 6 2020, 6:50 AM · Restricted Project

Jul 3 2020

madhur13490 added inline comments to D83100: [PPC][GlobalISel] Add initial GlobalIsel infrastructure.
Jul 3 2020, 10:12 AM · Restricted Project
madhur13490 added inline comments to D82713: Improve stack object printing..
Jul 3 2020, 1:35 AM · Restricted Project

Jul 2 2020

madhur13490 updated the diff for D83034: [GlobalISel] Don't skip adding predicate matcher.

Fix test failures

Jul 2 2020, 5:52 AM · Restricted Project
madhur13490 reclaimed D83034: [GlobalISel] Don't skip adding predicate matcher.
Jul 2 2020, 5:52 AM · Restricted Project
madhur13490 updated the summary of D83034: [GlobalISel] Don't skip adding predicate matcher.
Jul 2 2020, 5:52 AM · Restricted Project
madhur13490 abandoned D83034: [GlobalISel] Don't skip adding predicate matcher.
Jul 2 2020, 4:47 AM · Restricted Project
madhur13490 retitled D83034: [GlobalISel] Don't skip adding predicate matcher from [GlobalISel] Don't skip adding predicate macther to [GlobalISel] Don't skip adding predicate matcher.
Jul 2 2020, 4:15 AM · Restricted Project
madhur13490 retitled D83034: [GlobalISel] Don't skip adding predicate matcher from [GlobalISel] Don't skip adding predicate code to [GlobalISel] Don't skip adding predicate macther.
Jul 2 2020, 4:15 AM · Restricted Project
madhur13490 created D83034: [GlobalISel] Don't skip adding predicate matcher.
Jul 2 2020, 4:15 AM · Restricted Project
madhur13490 added inline comments to D82713: Improve stack object printing..
Jul 2 2020, 1:01 AM · Restricted Project

Jul 1 2020

madhur13490 updated the diff for D82713: Improve stack object printing..

rebase + address comments

Jul 1 2020, 5:22 AM · Restricted Project

Jun 28 2020

madhur13490 updated subscribers of D82713: Improve stack object printing..

@jlpeyton Any idea why the tests you added may be failing? I don't think it has anything related to my changes.

Jun 28 2020, 10:16 AM · Restricted Project
madhur13490 retitled D82713: Improve stack object printing. from NFC. Improve stack object printing. to Improve stack object printing..
Jun 28 2020, 9:43 AM · Restricted Project
madhur13490 updated the diff for D82713: Improve stack object printing..

fix tests

Jun 28 2020, 9:12 AM · Restricted Project
madhur13490 created D82713: Improve stack object printing..
Jun 28 2020, 5:29 AM · Restricted Project
madhur13490 committed rGc73966c2f792: Improve stack object printing. NFC. (authored by madhur13490).
Improve stack object printing. NFC.
Jun 28 2020, 4:57 AM
madhur13490 committed rG299dee91b347: Revert accidentally landed patch citing o build errors (authored by madhur13490).
Revert accidentally landed patch citing o build errors
Jun 28 2020, 4:57 AM
madhur13490 added a reverting change for rGc73966c2f792: Improve stack object printing. NFC.: rG299dee91b347: Revert accidentally landed patch citing o build errors.
Jun 28 2020, 4:57 AM
madhur13490 closed D82712: Improve stack object printing. NFC..
Jun 28 2020, 4:57 AM · Restricted Project
madhur13490 updated the diff for D82712: Improve stack object printing. NFC..

rebase

Jun 28 2020, 4:25 AM · Restricted Project
madhur13490 accepted D82712: Improve stack object printing. NFC..
Jun 28 2020, 4:25 AM · Restricted Project
madhur13490 created D82712: Improve stack object printing. NFC..
Jun 28 2020, 4:25 AM · Restricted Project
madhur13490 updated the diff for D82712: Improve stack object printing. NFC..

remove redundant print

Jun 28 2020, 4:25 AM · Restricted Project

Jun 25 2020

madhur13490 updated the summary of D82469: Take out resource tracking from ASM printer..
Jun 25 2020, 3:36 AM · Restricted Project
madhur13490 updated the diff for D82469: Take out resource tracking from ASM printer..

Address comments by arsenm, revise description

Jun 25 2020, 3:36 AM · Restricted Project

Jun 24 2020

madhur13490 created D82469: Take out resource tracking from ASM printer..
Jun 24 2020, 8:36 AM · Restricted Project

Jun 22 2020

madhur13490 added inline comments to D80713: [AMDGPU] Support disassembly for AMDGPU kernel descriptors.
Jun 22 2020, 6:57 AM · Restricted Project

Jun 21 2020

madhur13490 added inline comments to D80713: [AMDGPU] Support disassembly for AMDGPU kernel descriptors.
Jun 21 2020, 2:05 AM · Restricted Project

Jun 16 2020

madhur13490 added a comment to D81806: [DA] conservatively mark the join of every divergent branch.

I am a bit surprised this is necessary. Actually, join divergence in bb3 should come about as a result of propagateLoopDivergence for the [bb1, bb2] loop and not immediately because it is a divergent exit.

I am not sure what you mean here. propagateLoopDivergence is calling propagateJoinDivergence ... so doesn't that count as a result of the former?

Also, a divergent loop exit does not automatically become join divergent, eg:

bb1: 
   %m.uni = <uni>
   %n.uni = <uni>
   br <uni>, %bb2, %bb3

bb2: [..]
   br <div>, %bb2, %bb3

bb3:
   %x.uni = phi [%m.uni, %bb2], [%n.uni %bb1]  <-- divergent loop exit that is not join divergent

But here, bb3 is not a join block for the bb2 loop, since there is only one path from the loop exit reaching bb3.

Exactly. With this patch %x.uni is marked as join divergent even though it is uniform: In its present form the patch solves one issue at the cost of precision.

The real culprit here is the SDA::join_blocks interface that does not distinguish divergent join blocks and loop exits. The SDA "knows" which is which internally, loses that information as it passes divergent blocks through join_blocks and the DA has to reverse-engineer that information. I have an unfinished patch here that fixes that and should resolve the bug addressed by this patch as well. The unfinished patch also factors the back-and-forth between the DA and SDA to propagate along nested loops completely into the SDA (propagateLoopDiv does not really belong in the DA).

Long story short: This is an ok fix (but please add a FIXME/TODO that hints to the issues with this approach) but we should rework the join_blocks interface in any case.

Jun 16 2020, 6:37 AM · Restricted Project

Jun 5 2020

madhur13490 committed rGbca413b036bf: Fix a typo in AMDGPU docs (authored by madhur13490).
Fix a typo in AMDGPU docs
Jun 5 2020, 6:38 AM
madhur13490 closed D81247: Fix a typo in AMDGPU docs.
Jun 5 2020, 6:37 AM · Restricted Project
madhur13490 created D81247: Fix a typo in AMDGPU docs.
Jun 5 2020, 3:48 AM · Restricted Project

Jun 2 2020

madhur13490 updated the diff for D80711: Utility to dump .dot representation of SelectionDAG without firing viewer.

rebase

Jun 2 2020, 2:45 AM · Restricted Project

Jun 1 2020

madhur13490 added inline comments to D80920: AMDGPU: Fix alignment for dynamic allocas.
Jun 1 2020, 8:33 AM · Restricted Project

May 30 2020

madhur13490 updated the diff for D80711: Utility to dump .dot representation of SelectionDAG without firing viewer.

Address further comment by arsenm

May 30 2020, 9:46 PM · Restricted Project
madhur13490 added inline comments to D80711: Utility to dump .dot representation of SelectionDAG without firing viewer.
May 30 2020, 9:46 PM · Restricted Project

May 29 2020

madhur13490 updated the diff for D80711: Utility to dump .dot representation of SelectionDAG without firing viewer.

Fix clang-tidy errors

May 29 2020, 8:39 AM · Restricted Project
madhur13490 updated the diff for D80711: Utility to dump .dot representation of SelectionDAG without firing viewer.

Addressing comments by arsenm

May 29 2020, 4:18 AM · Restricted Project
madhur13490 added inline comments to D80711: Utility to dump .dot representation of SelectionDAG without firing viewer.
May 29 2020, 4:18 AM · Restricted Project

May 28 2020

madhur13490 updated the summary of D80711: Utility to dump .dot representation of SelectionDAG without firing viewer.
May 28 2020, 9:50 AM · Restricted Project
madhur13490 updated the diff for D80711: Utility to dump .dot representation of SelectionDAG without firing viewer.

Update summary

May 28 2020, 9:49 AM · Restricted Project
madhur13490 created D80711: Utility to dump .dot representation of SelectionDAG without firing viewer.
May 28 2020, 4:18 AM · Restricted Project