Page MenuHomePhabricator
Feed Advanced Search

Yesterday

daniel_a created D67876: Add support for using pass plugins from lld.
Sat, Sep 21, 4:52 AM · lld, Restricted Project

Wed, Sep 18

mattd created D67735: [lld][mach-o] Avoid segfaulting when handling an empty section list..
Wed, Sep 18, 3:00 PM · Restricted Project, lld
mattd retitled D67735: [lld][mach-o] Avoid segfaulting when handling an empty section list. from [lld][mach-o] Avoid segfaulting when handling an empty segment list. to [lld][mach-o] Avoid segfaulting when handling an empty section list..
Wed, Sep 18, 3:00 PM · Restricted Project, lld

Thu, Sep 12

avl updated the summary of D67469: [WIP][Debuginfo][LLD] Remove obsolete debug info while garbage collecting..
Thu, Sep 12, 7:37 AM · debug-info, lld, Restricted Project

Wed, Sep 11

avl added projects to D67469: [WIP][Debuginfo][LLD] Remove obsolete debug info while garbage collecting.: lld, debug-info.
Wed, Sep 11, 11:15 PM · debug-info, lld, Restricted Project

Tue, Sep 10

ruiu closed D66239: [LLD][COFF] Add index to disambiguate archive members when using -wholearchive .
Tue, Sep 10, 4:49 AM · Restricted Project, lld
zero9178 added a comment to D66239: [LLD][COFF] Add index to disambiguate archive members when using -wholearchive .

Friendly after a week ping.

Tue, Sep 10, 1:04 AM · Restricted Project, lld

Tue, Sep 3

zero9178 updated the diff for D66239: [LLD][COFF] Add index to disambiguate archive members when using -wholearchive .

Changed memberOffset to memberIndex as suggested by reviwer. Would need someone to commit this for me

Tue, Sep 3, 5:08 AM · Restricted Project, lld

Mon, Sep 2

ruiu accepted D66239: [LLD][COFF] Add index to disambiguate archive members when using -wholearchive .

LGTM with this change.

Mon, Sep 2, 1:12 AM · Restricted Project, lld

Fri, Aug 30

zero9178 updated the diff for D66239: [LLD][COFF] Add index to disambiguate archive members when using -wholearchive .

Changed index from std::uint64_t to int. Made test accept both kinds of slashes

Fri, Aug 30, 3:56 AM · Restricted Project, lld

Wed, Aug 28

ruiu added a comment to D66260: [lld][Hexagon] Add GOTREL relocations.

Where can we find a psABI describing these relocation types?

You can find it here: https://developer.qualcomm.com/download/hexagon/hexagon-application-binary-interface-specification.zip?referrer=node/6116
but there is a click-through license and registration.

Wed, Aug 28, 2:50 AM · Restricted Project, lld
MaskRay added a comment to D66260: [lld][Hexagon] Add GOTREL relocations.

Still having trouble to access this.

Wed, Aug 28, 2:25 AM · Restricted Project, lld

Aug 19 2019

sidneym closed D66260: [lld][Hexagon] Add GOTREL relocations.
Aug 19 2019, 6:32 AM · Restricted Project, lld
ruiu added inline comments to D66239: [LLD][COFF] Add index to disambiguate archive members when using -wholearchive .
Aug 19 2019, 4:39 AM · Restricted Project, lld
MaskRay closed D39324: [lld] Support TLS in RISC-V.
Aug 19 2019, 2:57 AM · lld
ruiu added a comment to D39324: [lld] Support TLS in RISC-V.

This has been merged on July 2 as http://reviews.llvm.org/rL364813

Aug 19 2019, 2:48 AM · lld
ruiu added a comment to D66105: Support HEX_32 when building shared objects.

LGTM

Aug 19 2019, 1:06 AM · Restricted Project, lld

Aug 18 2019

ruiu accepted D66260: [lld][Hexagon] Add GOTREL relocations.

LGTM

Aug 18 2019, 11:43 PM · Restricted Project, lld

Aug 16 2019

MaskRay accepted D66260: [lld][Hexagon] Add GOTREL relocations.
Aug 16 2019, 6:54 PM · Restricted Project, lld
sidneym closed D66105: Support HEX_32 when building shared objects.
Aug 16 2019, 8:35 AM · Restricted Project, lld

Aug 15 2019

sidneym added a comment to D66260: [lld][Hexagon] Add GOTREL relocations.

Where can we find a psABI describing these relocation types?

Aug 15 2019, 8:03 AM · Restricted Project, lld
sidneym updated the diff for D66260: [lld][Hexagon] Add GOTREL relocations.

Update filenames in testcase.

Aug 15 2019, 7:16 AM · Restricted Project, lld
MaskRay closed D39323: [lld] Support dynamic linking in RISC-V.

Am I correct in thinking that this functionality has already been upstreamed into LLD, and that this patch can now been abandoned?

Aug 15 2019, 3:14 AM · Restricted Project, lld
lenary added a comment to D39323: [lld] Support dynamic linking in RISC-V.

Am I correct in thinking that this functionality has already been upstreamed into LLD, and that this patch can now been abandoned?

Aug 15 2019, 2:52 AM · Restricted Project, lld
lenary added a comment to D39324: [lld] Support TLS in RISC-V.

Am I correct in thinking that this functionality has already been upstreamed into LLD, and that this patch can now been abandoned?

Aug 15 2019, 2:52 AM · lld

Aug 14 2019

MaskRay added inline comments to D66260: [lld][Hexagon] Add GOTREL relocations.
Aug 14 2019, 11:04 PM · Restricted Project, lld
MaskRay added a reviewer for D66260: [lld][Hexagon] Add GOTREL relocations: MaskRay.
Aug 14 2019, 9:16 PM · Restricted Project, lld
MaskRay added a comment to D66260: [lld][Hexagon] Add GOTREL relocations.

Where can we find a psABI describing these relocation types?

Aug 14 2019, 9:16 PM · Restricted Project, lld
sidneym created D66260: [lld][Hexagon] Add GOTREL relocations.
Aug 14 2019, 4:16 PM · Restricted Project, lld
zero9178 added a reviewer for D66239: [LLD][COFF] Add index to disambiguate archive members when using -wholearchive : pcc.
Aug 14 2019, 2:01 PM · Restricted Project, lld
zero9178 updated the diff for D66239: [LLD][COFF] Add index to disambiguate archive members when using -wholearchive .

Fixed test to show regression and verify output

Aug 14 2019, 1:15 PM · Restricted Project, lld
zero9178 edited projects for D66239: [LLD][COFF] Add index to disambiguate archive members when using -wholearchive , added: lld; removed Restricted Project.
Aug 14 2019, 12:38 PM · Restricted Project, lld
bcain accepted D66105: Support HEX_32 when building shared objects.
Aug 14 2019, 7:00 AM · Restricted Project, lld

Aug 13 2019

avl added a comment to D59553: [LLD][ELF][DebugInfo] llvm-symbolizer shows incorrect source line info if --gc-sections used.

Folks, I would like to ask a question related to this review and DWARF standard:

Aug 13 2019, 8:37 AM · lld, Restricted Project

Aug 12 2019

sidneym added a reviewer for D66105: Support HEX_32 when building shared objects: shankare.
Aug 12 2019, 12:45 PM · Restricted Project, lld
sidneym created D66105: Support HEX_32 when building shared objects.
Aug 12 2019, 12:41 PM · Restricted Project, lld

Aug 9 2019

ikudrin closed D65875: [ELF] For VS-style diagnostics, prefer using the full path..
Aug 9 2019, 1:28 AM · Restricted Project, lld
ruiu accepted D65875: [ELF] For VS-style diagnostics, prefer using the full path..

I confirmed that these tests are not affected by the actual path on a machine running the tests. I missed the part that you added .line directive in this patch. Thank you for doing this.

Aug 9 2019, 12:25 AM · Restricted Project, lld

Aug 8 2019

ikudrin added a comment to D65875: [ELF] For VS-style diagnostics, prefer using the full path..

Well, I have checked the patch on Windows. All tests pass.

Aug 8 2019, 6:31 AM · Restricted Project, lld
ikudrin added a comment to D65875: [ELF] For VS-style diagnostics, prefer using the full path..

We had that issue with D65810 (rL368153), windows build bots complained about different path separators. That was fixed in rL368169. Thus, I made similar adjustments in this patch.

Aug 8 2019, 3:39 AM · Restricted Project, lld
ruiu added a comment to D65875: [ELF] For VS-style diagnostics, prefer using the full path..

Generally looking good, but do these tests pass on Windows on which a path separator is \? It seems like you hardcoded / as a path separator in the tests.

Aug 8 2019, 2:58 AM · Restricted Project, lld

Aug 7 2019

ikudrin created D65875: [ELF] For VS-style diagnostics, prefer using the full path..
Aug 7 2019, 7:53 AM · Restricted Project, lld
ikudrin closed D65810: [ELF] Fix splitting messages for duplicate symbols..
Aug 7 2019, 4:33 AM · Restricted Project, lld
MaskRay accepted D65810: [ELF] Fix splitting messages for duplicate symbols..
Aug 7 2019, 3:09 AM · Restricted Project, lld
ruiu accepted D65810: [ELF] Fix splitting messages for duplicate symbols..

LGTM

Aug 7 2019, 2:12 AM · Restricted Project, lld

Aug 6 2019

ikudrin updated the diff for D65810: [ELF] Fix splitting messages for duplicate symbols..
  • Removed Inputs/vs-diagnostics-duplicate-split.s
  • Updated the test accordingly.
Aug 6 2019, 11:56 PM · Restricted Project, lld
MaskRay added inline comments to D65810: [ELF] Fix splitting messages for duplicate symbols..
Aug 6 2019, 9:55 PM · Restricted Project, lld
ikudrin created D65810: [ELF] Fix splitting messages for duplicate symbols..
Aug 6 2019, 8:36 AM · Restricted Project, lld
ikudrin closed D65639: [MachO] Update LLD to use 64-bit offsets with DataExtractor (3/5).
Aug 6 2019, 6:36 AM · Restricted Project, lld

Aug 2 2019

ruiu accepted D65639: [MachO] Update LLD to use 64-bit offsets with DataExtractor (3/5).

LGTM

Aug 2 2019, 2:36 AM · Restricted Project, lld
ikudrin added a child revision for D65639: [MachO] Update LLD to use 64-bit offsets with DataExtractor (3/5): D65641: Remove support for 32-bit offsets in utility classes (5/5).
Aug 2 2019, 2:15 AM · Restricted Project, lld
ikudrin added a parent revision for D65639: [MachO] Update LLD to use 64-bit offsets with DataExtractor (3/5): D65638: Switch LLVM to use 64-bit offsets (2/5).
Aug 2 2019, 2:07 AM · Restricted Project, lld
ikudrin created D65639: [MachO] Update LLD to use 64-bit offsets with DataExtractor (3/5).
Aug 2 2019, 2:07 AM · Restricted Project, lld

Jul 31 2019

ikudrin closed D65499: [ELF] Fix finding the location in messages for undefined hidden symbols..
Jul 31 2019, 10:24 PM · lld, Restricted Project
ruiu accepted D65499: [ELF] Fix finding the location in messages for undefined hidden symbols..

LGTM

Jul 31 2019, 6:23 PM · lld, Restricted Project
ikudrin updated the diff for D65499: [ELF] Fix finding the location in messages for undefined hidden symbols..
  • Combined all the suggestions to improve the regular expression.
  • Addressed @MaskRay's comments for the test.
Jul 31 2019, 2:10 AM · lld, Restricted Project

Jul 25 2019

ihalip abandoned D63564: Add undefined symbols from linker script to output file.

Abandoning this, it's obvious it wasn't the right fix anyway.

Jul 25 2019, 11:12 PM · Restricted Project, lld

Jul 11 2019

avl added a comment to D59553: [LLD][ELF][DebugInfo] llvm-symbolizer shows incorrect source line info if --gc-sections used.

Thank you, I apologize for impatience.

Jul 11 2019, 2:32 PM · lld, Restricted Project
echristo added a comment to D59553: [LLD][ELF][DebugInfo] llvm-symbolizer shows incorrect source line info if --gc-sections used.

I am following, I've just been out for 3 weeks. I'm catching up now and this is in my queue.

Jul 11 2019, 2:22 PM · lld, Restricted Project
avl added a comment to D59553: [LLD][ELF][DebugInfo] llvm-symbolizer shows incorrect source line info if --gc-sections used.

I'm fine with this patch. We've discussed a lot about what is a desirable value for a "null" for debug info, but looks like as long as it does not appear as a valid address, it should be fine.

Is Eric fine with this?

Jul 11 2019, 2:17 PM · lld, Restricted Project

Jul 8 2019

avl added a comment to D59553: [LLD][ELF][DebugInfo] llvm-symbolizer shows incorrect source line info if --gc-sections used.
Jul 8 2019, 8:06 AM · lld, Restricted Project

Jul 5 2019

MaskRay added a comment to D59553: [LLD][ELF][DebugInfo] llvm-symbolizer shows incorrect source line info if --gc-sections used.

Issues I noticed, some of which are possibly bugs, but it's hard to tell:

  • llvm-symbolizer reports the line number corresponding to the removed foo for the fourth case.
  • GNU addr2line line numbers are wrong in the first three cases, and foo is reported in the fourth.
  • GNU addr2line thinks foo is the right symbol for the fourth case, even though it has been removed. llvm-symbolizer just prints '??' (that's probably correct).

    I haven't checked to see how many of these issues are fixed by D60470.
Jul 5 2019, 6:50 AM · lld, Restricted Project
avl updated the diff for D59553: [LLD][ELF][DebugInfo] llvm-symbolizer shows incorrect source line info if --gc-sections used.

removed whitespaces, added handling x86 ILP32 case.

Jul 5 2019, 5:37 AM · lld, Restricted Project
thakis added inline comments to D50404: [lld-link] Generalize handling of /debug and /debug:{none,full,fastlink,ghash,symtab}.
Jul 5 2019, 4:28 AM · Restricted Project, lld
jhenderson added a comment to D59553: [LLD][ELF][DebugInfo] llvm-symbolizer shows incorrect source line info if --gc-sections used.

I disagree. For PIE output, 0 (__ehdr_start) points to the ELF header. It cannot be a valid code address. Note, the discussion is really about code addresses (DW_AT_low_pc, DW_AT_ranges, DW_AT_entry_pc, etc), not an unconstrained relocated file offset.

Not if the user is using linker scripts:

/* test.script */
PHDRS
{
    ph_load PT_LOAD FLAGS(0x1|0x2|0x4);
}
Jul 5 2019, 2:52 AM · lld, Restricted Project
MaskRay added a comment to D59553: [LLD][ELF][DebugInfo] llvm-symbolizer shows incorrect source line info if --gc-sections used.
In D59553#1571050, @avl wrote:

error: Invalid address range [0xfffffffffffffffe, 0x0000000000000004)

DW_AT_low_pc DW_AT_high_pc pairs like these are less ideal. Before, tools have learned 0 address is special. They may or may not need a special case to handle this. Now, -2 is introduced (whatever value we choose here, GNU linkers still either relocate these to 0 or use their CB_PRETEND logic). They need to learn one more rule. I still believe, teaching the symbolizers (addr2line, llvm-symbolizer D60470) is the way forward.

the point is in that tools should NOT learn one more rule. There should not be done any additional logic for UINT64_MAX-1 in tools. the fact that llvm-dwarfdump --verify displays error message is probably normal. Because debug info references not existed address range. llvm-dwarfdump --verify dislays errors for current solution also. The proper way to fix llvm-dwarfdump --verify is to remove broken debug info.

I agree. As things stand, some tools have special case behaviour for 0, but many do not, and consequently get it wrong. Furthermore, there are some cases where it is impossible to determine whether 0 is special or not. For example for PIE output, 0 can be a valid address (not all linker scripts place the headers in memory), meaning the tools can't distinguish between a function at address 0, or a dead piece of debug information.

Jul 5 2019, 2:23 AM · lld, Restricted Project
jhenderson added a comment to D59553: [LLD][ELF][DebugInfo] llvm-symbolizer shows incorrect source line info if --gc-sections used.
In D59553#1571050, @avl wrote:

error: Invalid address range [0xfffffffffffffffe, 0x0000000000000004)

DW_AT_low_pc DW_AT_high_pc pairs like these are less ideal. Before, tools have learned 0 address is special. They may or may not need a special case to handle this. Now, -2 is introduced (whatever value we choose here, GNU linkers still either relocate these to 0 or use their CB_PRETEND logic). They need to learn one more rule. I still believe, teaching the symbolizers (addr2line, llvm-symbolizer D60470) is the way forward.

the point is in that tools should NOT learn one more rule. There should not be done any additional logic for UINT64_MAX-1 in tools. the fact that llvm-dwarfdump --verify displays error message is probably normal. Because debug info references not existed address range. llvm-dwarfdump --verify dislays errors for current solution also. The proper way to fix llvm-dwarfdump --verify is to remove broken debug info.

Jul 5 2019, 2:03 AM · lld, Restricted Project

Jul 4 2019

avl added a comment to D59553: [LLD][ELF][DebugInfo] llvm-symbolizer shows incorrect source line info if --gc-sections used.

error: Invalid address range [0xfffffffffffffffe, 0x0000000000000004)

DW_AT_low_pc DW_AT_high_pc pairs like these are less ideal. Before, tools have learned 0 address is special. They may or may not need a special case to handle this. Now, -2 is introduced (whatever value we choose here, GNU linkers still either relocate these to 0 or use their CB_PRETEND logic). They need to learn one more rule. I still believe, teaching the symbolizers (addr2line, llvm-symbolizer D60470) is the way forward.

Jul 4 2019, 11:44 PM · lld, Restricted Project
MaskRay added a comment to D59553: [LLD][ELF][DebugInfo] llvm-symbolizer shows incorrect source line info if --gc-sections used.

I thought CB_PRETEND could fix a "error on relocations to discarded SHF_ALLOC sections" issue but I fixed it in another way. Let's ignore my comment about CB_PRETEND.

Jul 4 2019, 8:01 PM · lld, Restricted Project
rocallahan added a comment to D54747: Discard debuginfo for object files empty after GC.

Sorry for not responding earlier. Phabricator insists on sending me emails about all issues in the system, and I never figured out how to get GMail to show me only emails about Phabricator issues I'm CCed on.

Jul 4 2019, 2:16 PM · Restricted Project, lld
thakis added inline comments to D50404: [lld-link] Generalize handling of /debug and /debug:{none,full,fastlink,ghash,symtab}.
Jul 4 2019, 2:14 PM · Restricted Project, lld
Herald added a project to D50404: [lld-link] Generalize handling of /debug and /debug:{none,full,fastlink,ghash,symtab}: Restricted Project.
Jul 4 2019, 2:04 PM · Restricted Project, lld
avl added a comment to D59553: [LLD][ELF][DebugInfo] llvm-symbolizer shows incorrect source line info if --gc-sections used.

@jhenderson Thank you for pointing this out! Actually --verify complains about errors in both cases(with the fix and without the fix) for the testcase from this review:

Jul 4 2019, 10:43 AM · lld, Restricted Project

Jul 3 2019

jhenderson added a comment to D59553: [LLD][ELF][DebugInfo] llvm-symbolizer shows incorrect source line info if --gc-sections used.

@avl, something you might want to watch out for is the behaviour of llvm-dwarfdump --verify where this patching has happened. I've seen it spit out complaints about "invalid address ranges" for this situation.

Jul 3 2019, 8:21 AM · lld, Restricted Project

Jun 28 2019

ikudrin closed D63869: [ELF] Do not produce DT_JMPREL and DT_PLTGOT if .rela.plt is empty..
Jun 28 2019, 3:16 AM · Restricted Project, lld
grimar accepted D63869: [ELF] Do not produce DT_JMPREL and DT_PLTGOT if .rela.plt is empty..

LGTM

Jun 28 2019, 2:02 AM · Restricted Project, lld
ikudrin updated the diff for D63869: [ELF] Do not produce DT_JMPREL and DT_PLTGOT if .rela.plt is empty..
  • Extended the test and moved it into the linkerscript folder.
Jun 28 2019, 12:54 AM · Restricted Project, lld

Jun 27 2019

MaskRay added a reviewer for D63869: [ELF] Do not produce DT_JMPREL and DT_PLTGOT if .rela.plt is empty.: MaskRay.
Jun 27 2019, 9:12 PM · Restricted Project, lld
MaskRay added inline comments to D63869: [ELF] Do not produce DT_JMPREL and DT_PLTGOT if .rela.plt is empty..
Jun 27 2019, 7:18 AM · Restricted Project, lld
MaskRay added inline comments to D63869: [ELF] Do not produce DT_JMPREL and DT_PLTGOT if .rela.plt is empty..
Jun 27 2019, 6:55 AM · Restricted Project, lld
grimar added a comment to D63869: [ELF] Do not produce DT_JMPREL and DT_PLTGOT if .rela.plt is empty..
  • Reworked the test. I am not sure about moving it into linkerscript, though, because it does not test the support for linker scripts per se.
Jun 27 2019, 5:08 AM · Restricted Project, lld
ikudrin added inline comments to D63869: [ELF] Do not produce DT_JMPREL and DT_PLTGOT if .rela.plt is empty..
Jun 27 2019, 4:55 AM · Restricted Project, lld
ikudrin updated the diff for D63869: [ELF] Do not produce DT_JMPREL and DT_PLTGOT if .rela.plt is empty..
  • Reworked the test.

I am not sure about moving it into linkerscript, though, because it does not test the support for linker scripts per se. Moreover, there are lots of tests in the main test folder which also use linker scripts.

Jun 27 2019, 4:50 AM · Restricted Project, lld
MaskRay added inline comments to D63869: [ELF] Do not produce DT_JMPREL and DT_PLTGOT if .rela.plt is empty..
Jun 27 2019, 4:41 AM · Restricted Project, lld
MaskRay added inline comments to D63869: [ELF] Do not produce DT_JMPREL and DT_PLTGOT if .rela.plt is empty..
Jun 27 2019, 4:33 AM · Restricted Project, lld
grimar added a comment to D63869: [ELF] Do not produce DT_JMPREL and DT_PLTGOT if .rela.plt is empty..

I think this test case should live in test\ELF\linkerscript folder. Also it should be .test, not .s,
like our other tests that has no or little amount of asm code.
(See unused-synthetic2.test for example)

Jun 27 2019, 4:24 AM · Restricted Project, lld
ruiu accepted D63869: [ELF] Do not produce DT_JMPREL and DT_PLTGOT if .rela.plt is empty..

LGTM

Jun 27 2019, 4:20 AM · Restricted Project, lld
ikudrin added a comment to D63869: [ELF] Do not produce DT_JMPREL and DT_PLTGOT if .rela.plt is empty..

On Linux, the issue can be reproduced in the following way:

Jun 27 2019, 4:20 AM · Restricted Project, lld
ikudrin created D63869: [ELF] Do not produce DT_JMPREL and DT_PLTGOT if .rela.plt is empty..
Jun 27 2019, 4:11 AM · Restricted Project, lld

Jun 26 2019

aganea closed D63775: [LLD][COFF] Case insensitive compares for /nodefaultlib.
Jun 26 2019, 8:40 AM · Restricted Project, lld
ruiu accepted D63775: [LLD][COFF] Case insensitive compares for /nodefaultlib.

LGTM

Jun 26 2019, 4:30 AM · Restricted Project, lld
avl added a comment to D59553: [LLD][ELF][DebugInfo] llvm-symbolizer shows incorrect source line info if --gc-sections used.

@MaskRay Hi MaskRay, PRETEND is a connected but separate issue. I agree it would be good to implement some kind of the PRETEND/CB_PRETEND logic in lld. But it does not make obsolete this patch. implementing of PRETEND logic answers the question "how to select proper debug info for COMDAT section". That patch answers the question "How to avoid overlapping address ranges in case debug info referenced to deleted code presented". This patch makes sense not only for PRETEND. Thus, I do not agree with "If we have PRETEND, we will not need the -2 hack in relocateNonAlloc". Let`s not mixup issues.

Jun 26 2019, 3:16 AM · lld, Restricted Project

Jun 25 2019

rnk accepted D63775: [LLD][COFF] Case insensitive compares for /nodefaultlib.

lgtm

Jun 25 2019, 3:47 PM · Restricted Project, lld
aganea updated the diff for D63775: [LLD][COFF] Case insensitive compares for /nodefaultlib.

Case-insensitive on Linux as requested.

Jun 25 2019, 3:09 PM · Restricted Project, lld
rnk added a comment to D63775: [LLD][COFF] Case insensitive compares for /nodefaultlib.

I guess /nodefaultlib just isn't that common compared to /defaultlib, so this hadn't been reported yet. Fix makes sense to me.

Jun 25 2019, 11:25 AM · Restricted Project, lld
aganea updated the diff for D63775: [LLD][COFF] Case insensitive compares for /nodefaultlib.

Updated test.

Jun 25 2019, 9:09 AM · Restricted Project, lld
aganea created D63775: [LLD][COFF] Case insensitive compares for /nodefaultlib.
Jun 25 2019, 9:05 AM · Restricted Project, lld
MaskRay added a comment to D59553: [LLD][ELF][DebugInfo] llvm-symbolizer shows incorrect source line info if --gc-sections used.
In D59553#1557151, @avl wrote:
Jun 25 2019, 8:51 AM · lld, Restricted Project
avl added a comment to D59553: [LLD][ELF][DebugInfo] llvm-symbolizer shows incorrect source line info if --gc-sections used.

ping @echristo

Jun 25 2019, 2:03 AM · lld, Restricted Project

Jun 21 2019

lebedev.ri abandoned D41159: [asan] LIT: Add lld testing config..
Jun 21 2019, 8:50 AM · Restricted Project, lld, Restricted Project