date:20170719

[llvm-bugs] [Bug 20806] [EarlyCSE, GVN, Missed Opt] invariant loads can be forwarded across aliasing stores

2017-07-19 Thread via llvm-bugs

https://bugs.llvm.org/show_bug.cgi?id=20806

Geoff Berry  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 CC||gbe...@codeaurora.org
 Status|NEW |RESOLVED

--- Comment #2 from Geoff Berry  ---
The EarlyCSE case has been implemented for some time, even without MemorySSA.
It looks like the wrong GVN test case was mistakenly attached (since it has no
occurrences of invariant.load), but this optimization has also been implemented
in GVN (see llvm/test/Transforms/GVN/PRE/invariant-load.ll).

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

[llvm-bugs] [Bug 25012] Assert in early-cse: (New->getType() == getType() && "replaceAllUses of value with new value of different type!")

2017-07-19 Thread via llvm-bugs

https://bugs.llvm.org/show_bug.cgi?id=25012

Geoff Berry  changed:

   What|Removed |Added

 CC||gbe...@codeaurora.org
 Status|NEW |RESOLVED
 Resolution|--- |WORKSFORME

--- Comment #1 from Geoff Berry  ---
This seems to have been fixed some time in the last two years.

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

[llvm-bugs] [Bug 23214] [META] Using LLD as FreeBSD's system linker

2017-07-19 Thread via llvm-bugs

https://bugs.llvm.org/show_bug.cgi?id=23214
Bug 23214 depends on bug 28414, which changed state.

Bug 28414 Summary: lld can't be used with GCC 7
https://bugs.llvm.org/show_bug.cgi?id=28414

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

[llvm-bugs] [Bug 28414] lld can't be used with GCC 7

2017-07-19 Thread via llvm-bugs

https://bugs.llvm.org/show_bug.cgi?id=28414

Rafael Ávila de Espíndola  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED

--- Comment #32 from Rafael Ávila de Espíndola  ---
As of r308492 every issue listed here other than version references has been
fixed.

Since dropping support for version references was an explicit decision, I am
closing this for now.

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

[llvm-bugs] [Bug 33818] segfault in opt

2017-07-19 Thread via llvm-bugs

https://bugs.llvm.org/show_bug.cgi?id=33818

Davide Italiano  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|REOPENED|RESOLVED

--- Comment #14 from Davide Italiano  ---
Went away. Thanks for you report!

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

[llvm-bugs] [Bug 26322] Core load hangs

2017-07-19 Thread via llvm-bugs

https://bugs.llvm.org/show_bug.cgi?id=26322

Ankit Kothana  changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|FIXED   |---

--- Comment #5 from Ankit Kothana  ---
Any update on this??

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

[llvm-bugs] [Bug 23214] [META] Using LLD as FreeBSD's system linker

2017-07-19 Thread via llvm-bugs

https://bugs.llvm.org/show_bug.cgi?id=23214
Bug 23214 depends on bug 33766, which changed state.

Bug 33766 Summary: Implement filter library support (-F / --filter)
https://bugs.llvm.org/show_bug.cgi?id=33766

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
 Resolution|--- |FIXED

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

[llvm-bugs] [Bug 33766] Implement filter library support (-F / --filter)

2017-07-19 Thread via llvm-bugs

https://bugs.llvm.org/show_bug.cgi?id=33766

George Rimar  changed:

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
 Resolution|--- |FIXED

--- Comment #6 from George Rimar  ---
r308167

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

[llvm-bugs] [Bug 33847] New: Clang fails to properly find the gcc installation when cross-compiling

2017-07-19 Thread via llvm-bugs

https://bugs.llvm.org/show_bug.cgi?id=33847

Bug ID: 33847
   Summary: Clang fails to properly find the gcc installation when
cross-compiling
   Product: clang
   Version: trunk
  Hardware: PC
OS: Linux
Status: NEW
  Severity: normal
  Priority: P
 Component: Driver
  Assignee: unassignedclangb...@nondot.org
  Reporter: jacekswi...@gmail.com
CC: llvm-bugs@lists.llvm.org

Files like crtbegin.o and libgcc.a cannot be found by clang 5.0 while it worked
just fine for clang 4.0 and older releases. Using the following command fails
with clang from trunk with the message indicating missing crtbegin and libgcc:

clang -mthumb -mfloat-abi=hard -mfpu=neon-vfpv4 -mcpu=cortex-a15
--target=arm-poky-linux-gnueabi --gcc-toolchain=/usr
--sysroot= -B/usr/bin/arm-poky-linux-gnueabi
test.c -v

I can see that there is some issue with finding gcc toolchain as the verbose
output is missing few lines:

```
Found candidate GCC installation:
/usr/lib/gcc/arm-poky-linux-gnueabi/5.4.0
```

The same command works with older clangs and give verbose output:

```
Found candidate GCC installation:
/usr/lib/arm-poky-linux-gnueabi/5.4.0
Found candidate GCC installation:
/usr/lib/gcc/arm-poky-linux-gnueabi/5.4.0
Selected GCC installation:
/usr/lib/arm-poky-linux-gnueabi/5.4.0
Candidate multilib: .;@m32
Selected multilib: .;@m32
```

Adding -print-search-dirs gives similar results - clang 5.0:
```
programs: =
/bin:
/..//bin

libraries: =
/lib/clang/5.0.0:
/lib/../lib:
/usr/lib/arm-poky-linux-gnueabi:
/usr/lib/../lib:
/lib:
/usr/lib
```

and clang 4.0:
```
programs: =
/bin:
/usr/lib/arm-poky-linux-gnueabi/5.4.0/../../../arm-poky-linux-gnueabi/bin

libraries: =
/bin/../lib/clang/4.0.1:
/usr/lib/arm-poky-linux-gnueabi/5.4.0:
/usr/lib/arm-poky-linux-gnueabi/5.4.0/../../arm-poky-linux-gnueabi:
/usr/lib/arm-poky-linux-gnueabi/5.4.0/../../../lib:
/lib/../lib:
/usr/lib/arm-poky-linux-gnueabi:
/usr/lib/../lib:
/usr/lib/arm-poky-linux-gnueabi/../../lib:
/usr/lib/arm-poky-linux-gnueabi/5.4.0/../..:
/lib:
/usr/lib
```

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

[llvm-bugs] [Bug 26322] Core load hangs

2017-07-19 Thread via llvm-bugs

https://bugs.llvm.org/show_bug.cgi?id=26322

lab...@google.com changed:

   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution|--- |FIXED

--- Comment #6 from lab...@google.com ---
(In reply to Ankit Kothana from comment #5)
> Any update on this??

This problem is already fixed in lldb 4.0. There will not be another 3.9
release, so there is nothing we can do about older versions. I'd suggest
updating to lldb 4.0, or speaking to your distro if they would be willing to
backport the fix.

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

[llvm-bugs] [Bug 33848] New: X86 Asm does not support symbolic names inside address calculation

2017-07-19 Thread via llvm-bugs

https://bugs.llvm.org/show_bug.cgi?id=33848

Bug ID: 33848
   Summary: X86 Asm does not support symbolic names inside address
calculation
   Product: tools
   Version: trunk
  Hardware: PC
OS: All
Status: NEW
  Severity: enhancement
  Priority: P
 Component: llvm-as
  Assignee: unassignedb...@nondot.org
  Reporter: andrew.v.tische...@gmail.com
CC: llvm-bugs@lists.llvm.org

When we deal with complex address expression like 

  [foo + scale * RAX + RDX]

the current implementation does not support at least the following:

1. The negative number as symbolic name: see PR3367
   .set one 1
   lea rdx, [rax - one]
2. The scale as symbolic name
   .set scale, 4
   12345 + scale * RAX + RDX
3. Two different symbolic names in one expression
   foo + scale * RAX + RDX
4. It crashes when bogus scale value is used: see PR33661
   lea  rdx, [rax + -1*rcx]
5. In addition it depends on arguments order
6.1. And there is some "pseudo" interpreter to calculate the primitive
expressions like +, -, *, /, etc. This interpreter has assertion to use
immediates for all ops except plus and minus. As result in ops like [rax - one]
it assumes that rax has value 0 in all cases but why? It seems it's wrong.
6.2. And the second about the same: the assertions should be replaced with
error messages because currently we simply see the compiler crash instead of
any diagnostic.

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

[llvm-bugs] [Bug 33831] cfi-icall + ThinLTO program containing indirect call to inline function fails to link

2017-07-19 Thread via llvm-bugs

https://bugs.llvm.org/show_bug.cgi?id=33831

Peter Collingbourne  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED

--- Comment #1 from Peter Collingbourne  ---
r308504

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

[llvm-bugs] [Bug 33852] New: Defining __STDC_WANT_LIB_EXT1__ causes reserved-id-macro warning

2017-07-19 Thread via llvm-bugs

https://bugs.llvm.org/show_bug.cgi?id=33852

Bug ID: 33852
   Summary: Defining __STDC_WANT_LIB_EXT1__ causes
reserved-id-macro warning
   Product: clang
   Version: 4.0
  Hardware: Macintosh
OS: MacOS X
Status: NEW
  Severity: enhancement
  Priority: P
 Component: Frontend
  Assignee: unassignedclangb...@nondot.org
  Reporter: mohd.ak...@outlook.com
CC: llvm-bugs@lists.llvm.org

Doing this:

#define __STDC_WANT_LIB_EXT1__ 1

causes:

warning: macro name is a reserved identifier [-Wreserved-id-macro]

Defining __STDC_WANT_LIB_EXT1__ is valid in C11.

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

[llvm-bugs] [Bug 20805] [EarlyCSE, Missed Opt] Don't need to advance generation number unless mayalias

2017-07-19 Thread via llvm-bugs

https://bugs.llvm.org/show_bug.cgi?id=20805

Geoff Berry  changed:

   What|Removed |Added

 CC||gbe...@codeaurora.org
 Status|NEW |RESOLVED
 Resolution|--- |FIXED

--- Comment #1 from Geoff Berry  ---
Cases like this are now optimized by EarlyCSE w/ MemorySSA

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

[llvm-bugs] [Bug 23214] [META] Using LLD as FreeBSD's system linker

2017-07-19 Thread via llvm-bugs

https://bugs.llvm.org/show_bug.cgi?id=23214
Bug 23214 depends on bug 33820, which changed state.

Bug 33820 Summary: After r307364, some versioned symbols do not appear in .so 
files
https://bugs.llvm.org/show_bug.cgi?id=33820

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

[llvm-bugs] [Bug 33820] After r307364, some versioned symbols do not appear in .so files

2017-07-19 Thread via llvm-bugs

https://bugs.llvm.org/show_bug.cgi?id=33820

Rafael Ávila de Espíndola  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|NEW |RESOLVED

--- Comment #6 from Rafael Ávila de Espíndola  ---
Fixed in r308492.

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

[llvm-bugs] [Bug 33849] New: [meta] 5.0.0 Release Blockers

2017-07-19 Thread via llvm-bugs

https://bugs.llvm.org/show_bug.cgi?id=33849

Bug ID: 33849
   Summary: [meta] 5.0.0 Release Blockers
   Product: new-bugs
   Version: 5.0
  Hardware: All
OS: All
Status: NEW
  Severity: release blocker
  Priority: P
 Component: new bugs
  Assignee: unassignedb...@nondot.org
  Reporter: h...@chromium.org
CC: llvm-bugs@lists.llvm.org

This is the tracking bug for blockers of the 5.0.0 release.

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

[llvm-bugs] [Bug 33850] New: Update cxx_dr_status.html for 5.0.0

2017-07-19 Thread via llvm-bugs

https://bugs.llvm.org/show_bug.cgi?id=33850

Bug ID: 33850
   Summary: Update cxx_dr_status.html for 5.0.0
   Product: clang
   Version: unspecified
  Hardware: PC
OS: Linux
Status: NEW
  Severity: enhancement
  Priority: P
 Component: Documentation
  Assignee: unassignedclangb...@nondot.org
  Reporter: h...@chromium.org
CC: llvm-bugs@lists.llvm.org, richard-l...@metafoo.co.uk
Blocks: 33849

Richard, can you update cxx_dr_status.html 5.0.0?


Referenced Bugs:

https://bugs.llvm.org/show_bug.cgi?id=33849
[Bug 33849] [meta] 5.0.0 Release Blockers
-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

[llvm-bugs] [Bug 33851] New: update .abilist files for 5.0

2017-07-19 Thread via llvm-bugs

https://bugs.llvm.org/show_bug.cgi?id=33851

Bug ID: 33851
   Summary: update .abilist files for 5.0
   Product: libc++
   Version: unspecified
  Hardware: PC
OS: Linux
Status: NEW
  Severity: enhancement
  Priority: P
 Component: All Bugs
  Assignee: unassignedclangb...@nondot.org
  Reporter: h...@chromium.org
CC: e...@efcs.ca, llvm-bugs@lists.llvm.org,
mclow.li...@gmail.com
Blocks: 33849

Eric, can you help with this?


Referenced Bugs:

https://bugs.llvm.org/show_bug.cgi?id=33849
[Bug 33849] [meta] 5.0.0 Release Blockers
-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

[llvm-bugs] [Bug 33854] New: LLVM tools are not playing Visual Studio debugger friendly

2017-07-19 Thread via llvm-bugs

https://bugs.llvm.org/show_bug.cgi?id=33854

Bug ID: 33854
   Summary: LLVM tools are not playing Visual Studio debugger
friendly
   Product: clang
   Version: unspecified
  Hardware: PC
OS: Windows NT
Status: NEW
  Severity: enhancement
  Priority: P
 Component: Frontend
  Assignee: unassignedclangb...@nondot.org
  Reporter: juj...@gmail.com
CC: llvm-bugs@lists.llvm.org

It looks like the various tools in the Clang toolchain are set to internally
capture all crash signals and generate crash minidumps from them. This prevents
from being able to attach a Visual Studio debugger at the time of crash. By
default if applications do not register any signal handlers, the VC runtime
will pop up a debug handler dialog asking to attach a VS debugger in Debug
builds.

Would it be possible to make it so that Debug CMake config build would by
default not attach crash handlers, so that VC runtime would pop up the debugger
dialog? Additionally, it would be good to hook onto an environment variable,
say LLVM_DISABLE_CRASH_HANDLERS=1, which if set, would cause LLVM to hand off
to Visual Studio debugging.

Now I notice I need to do custom builds that comment out the crash handlers,
e.g. for llc.exe, in llc.cpp:

int main(int argc, char **argv) {
//  sys::PrintStackTraceOnErrorSignal(argv[0]);

It would be nice for LLVM to behave debugger friendly out of the box.

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

[llvm-bugs] [Bug 33788] Move TailRecursionElimination to new OptRemark API

2017-07-19 Thread via llvm-bugs

https://bugs.llvm.org/show_bug.cgi?id=33788

Davide Italiano  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|NEW |RESOLVED

--- Comment #2 from Davide Italiano  ---
r308524

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

[llvm-bugs] [Bug 33789] Remove old OptRemark API

2017-07-19 Thread via llvm-bugs

https://bugs.llvm.org/show_bug.cgi?id=33789
Bug 33789 depends on bug 33788, which changed state.

Bug 33788 Summary: Move TailRecursionElimination to new OptRemark API
https://bugs.llvm.org/show_bug.cgi?id=33788

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

[llvm-bugs] [Bug 33856] New: clang ignores #pragma CX_LIMITED_RANGE

2017-07-19 Thread via llvm-bugs

https://bugs.llvm.org/show_bug.cgi?id=33856

Bug ID: 33856
   Summary: clang ignores #pragma CX_LIMITED_RANGE
   Product: clang
   Version: 3.8
  Hardware: PC
OS: All
Status: NEW
  Severity: enhancement
  Priority: P
 Component: -New Bugs
  Assignee: unassignedclangb...@nondot.org
  Reporter: smcal...@gmail.com
CC: llvm-bugs@lists.llvm.org

At least on clang 3.8.0-2 (Ubuntu 16.04), this code:

//#pragma CX_LIMITED_RANGE on

#include 
#include 
#include 

int main() {
float complex a = rand() + I*rand();
float complex b = rand() + I*rand();
float complex c = a*b;
printf("res: %f,%f\n", __real__ c, __imag__ c);
}

generates identical assembly with and without the pragma on.  I'm not sure the
implementation is _required_ to simplify complex arithmetic with it on, but I
think that's the spirit of the standard.

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

[llvm-bugs] [Bug 32282] Assertion `loBit <= BitWidth && "loBit out of range"' failed with -O0 -march=skx.

2017-07-19 Thread via llvm-bugs

https://bugs.llvm.org/show_bug.cgi?id=32282

Davide Italiano  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|REOPENED|RESOLVED

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

[llvm-bugs] [Bug 33855] New: add support for icf=safe

2017-07-19 Thread via llvm-bugs

https://bugs.llvm.org/show_bug.cgi?id=33855

Bug ID: 33855
   Summary: add support for icf=safe
   Product: lld
   Version: unspecified
  Hardware: All
OS: Linux
Status: NEW
  Severity: enhancement
  Priority: P
 Component: ELF
  Assignee: unassignedb...@nondot.org
  Reporter: lloz...@chromium.org
CC: llvm-bugs@lists.llvm.org

This is a request to add --icf=safe or similar functionality. 

This flag was identified as one of missing functionality while trying to build
android with LLD.

In talking to Rui Ueyama, he suggested the following:

"The plan we were discussing is to make clang emit attribute for each function
whether its address is taken or not, so that the linker can merge functions
only when their addresses are not taken."

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

[llvm-bugs] [Bug 20806] [EarlyCSE, GVN, Missed Opt] invariant loads can be forwarded across aliasing stores

[llvm-bugs] [Bug 25012] Assert in early-cse: (New->getType() == getType() && "replaceAllUses of value with new value of different type!")

[llvm-bugs] [Bug 23214] [META] Using LLD as FreeBSD's system linker

[llvm-bugs] [Bug 28414] lld can't be used with GCC 7

[llvm-bugs] [Bug 33818] segfault in opt

[llvm-bugs] [Bug 26322] Core load hangs

[llvm-bugs] [Bug 23214] [META] Using LLD as FreeBSD's system linker

[llvm-bugs] [Bug 33766] Implement filter library support (-F / --filter)

[llvm-bugs] [Bug 33847] New: Clang fails to properly find the gcc installation when cross-compiling

[llvm-bugs] [Bug 26322] Core load hangs

[llvm-bugs] [Bug 33848] New: X86 Asm does not support symbolic names inside address calculation

[llvm-bugs] [Bug 33831] cfi-icall + ThinLTO program containing indirect call to inline function fails to link

[llvm-bugs] [Bug 33852] New: Defining __STDC_WANT_LIB_EXT1__ causes reserved-id-macro warning

[llvm-bugs] [Bug 20805] [EarlyCSE, Missed Opt] Don't need to advance generation number unless mayalias

[llvm-bugs] [Bug 23214] [META] Using LLD as FreeBSD's system linker

[llvm-bugs] [Bug 33820] After r307364, some versioned symbols do not appear in .so files

[llvm-bugs] [Bug 33849] New: [meta] 5.0.0 Release Blockers

[llvm-bugs] [Bug 33850] New: Update cxx_dr_status.html for 5.0.0

[llvm-bugs] [Bug 33851] New: update .abilist files for 5.0

[llvm-bugs] [Bug 33854] New: LLVM tools are not playing Visual Studio debugger friendly

[llvm-bugs] [Bug 33788] Move TailRecursionElimination to new OptRemark API

[llvm-bugs] [Bug 33789] Remove old OptRemark API

[llvm-bugs] [Bug 33856] New: clang ignores #pragma CX_LIMITED_RANGE

[llvm-bugs] [Bug 32282] Assertion `loBit <= BitWidth && "loBit out of range"' failed with -O0 -march=skx.

[llvm-bugs] [Bug 33855] New: add support for icf=safe

25 matches

Site Navigation

Mail list logo

Footer information