[llvm-bugs] [Bug 35295] New: Potential improvement for vectorization of sub

2017-11-14 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=35295

Bug ID: 35295
   Summary: Potential improvement for vectorization of sub
   Product: libraries
   Version: trunk
  Hardware: PC
OS: Windows NT
Status: NEW
  Severity: enhancement
  Priority: P
 Component: Backend: X86
  Assignee: unassignedb...@nondot.org
  Reporter: serguei.kat...@azul.com
CC: llvm-bugs@lists.llvm.org

Hi,

I'm not sure that the example below is valid but still I'd like to understand
difference in vectorizer behavior for add and sub.

Let consider two following c++ functions (https://godbolt.org/g/WxjdMP):
void testAdd(signed char a[], int N, signed int k) {
  for (int i = 0; i < N; i++)
a[i] += k;
}
void testSub(signed char a[], int N, signed int k) {
  for (int i = 0; i < N; i++)
a[i] -= k;
}

for testAdd vectorizer is able to utilize packed byte size paddb instruction
while for sub it is not. Instead it uses psubd resulting in a big additional
code to convert vector of i8 to vector of i32 and vice versa.

I wonder whether it is possible to utilize psubb for the second case.
I noticed that both gcc and icc is able to do that...

-- 
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 35296] New: [LoopUnroll / DT] "DominatorTree is not up to date" if -unroll-runtime-multi-exit given

2017-11-14 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=35296

Bug ID: 35296
   Summary: [LoopUnroll / DT]  "DominatorTree is not up to date"
if -unroll-runtime-multi-exit given
   Product: libraries
   Version: trunk
  Hardware: PC
OS: Linux
Status: NEW
  Severity: enhancement
  Priority: P
 Component: Scalar Optimizations
  Assignee: unassignedb...@nondot.org
  Reporter: pauls...@linux.vnet.ibm.com
CC: llvm-bugs@lists.llvm.org

Created attachment 19419
  --> https://bugs.llvm.org/attachment.cgi?id=19419&action=edit
reduced testcase

bin/opt -S -mtriple=s390x-linux-gnu -mcpu=z13 tc_domtree.ll -O3
-unroll-runtime-multi-exit

Discovered on SPEC, merely by passing 'unroll-runtime-multi-exit'.

-- 
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 32621] [mc] VOP3 version of v_interp_* should be supported for VI

2017-11-14 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=32621

Dmitry  changed:

   What|Removed |Added

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

--- Comment #1 from Dmitry  ---
Closed by commit 310251
http://llvm.org/viewvc/llvm-project?view=revision&revision=310251

-- 
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 30931] error: invalid instruction mnemonic 'movsl'

2017-11-14 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=30931

Amine Khaldi  changed:

   What|Removed |Added

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

--- Comment #4 from Amine Khaldi  ---
Thank you for the confirmation.

-- 
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 6815] [META] Compiling ReactOS with clang

2017-11-14 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=6815
Bug 6815 depends on bug 30931, which changed state.

Bug 30931 Summary: error: invalid instruction mnemonic 'movsl'
https://bugs.llvm.org/show_bug.cgi?id=30931

   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 10988] x86 MC encoder and disassembler bugs umbrella

2017-11-14 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=10988
Bug 10988 depends on bug 30931, which changed state.

Bug 30931 Summary: error: invalid instruction mnemonic 'movsl'
https://bugs.llvm.org/show_bug.cgi?id=30931

   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 35298] New: Provide a way to add spaces inside an initalizer list when formatting

2017-11-14 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=35298

Bug ID: 35298
   Summary: Provide a way to add spaces inside an initalizer list
when formatting
   Product: clang
   Version: 5.0
  Hardware: Macintosh
OS: MacOS X
Status: NEW
  Severity: enhancement
  Priority: P
 Component: Formatter
  Assignee: unassignedclangb...@nondot.org
  Reporter: hughbell...@gmail.com
CC: djas...@google.com, kli...@google.com,
llvm-bugs@lists.llvm.org

E.g.

static CapClass vtable = { CustomLineCapTypeAdjustableArrow,
   gdip_adjust_arrowcap_setup,
   gdip_adjust_arrowcap_clone_cap,
   gdip_adjust_arrowcap_destroy,
   gdip_adjust_arrowcap_draw };

Formatting this code with clang-format removes the spaces inside the
initializer list:

static CapClass vtable = {CustomLineCapTypeAdjustableArrow,
  gdip_adjust_arrowcap_setup,
  gdip_adjust_arrowcap_clone_cap,
  gdip_adjust_arrowcap_destroy,
  gdip_adjust_arrowcap_draw};


Please provide a way (e.g. something like SpacesInSquareBrackets) to provide
the functionality to add spaces inside an initializer list.

-- 
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 35299] New: Potential improvement for Loop Vectorization: XMM vs YMM vs ZMM

2017-11-14 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=35299

Bug ID: 35299
   Summary: Potential improvement for Loop Vectorization: XMM vs
YMM vs ZMM
   Product: libraries
   Version: trunk
  Hardware: PC
OS: Windows NT
Status: NEW
  Severity: enhancement
  Priority: P
 Component: Backend: X86
  Assignee: unassignedb...@nondot.org
  Reporter: serguei.kat...@azul.com
CC: llvm-bugs@lists.llvm.org

What is motivation to choose the lowest Vectorization Factor for equal vector
cost?

Specifically in LoopVectorizationCostModel::selectVectorizationFactor(unsigned
MaxVF):
  for (unsigned i = 2; i <= MaxVF; i *= 2) {
...
if (VectorCost < Cost) {
  Cost = VectorCost;
  Width = i;
}
  }
...
  VectorizationFactor Factor = {Width, (unsigned)(Width * Cost)};
  return Factor;


So we update vectorization factor to higher value only if the cost is strongly
less than previous computed cost.

So if the computed vectorization cost is equal for XMM, YMM and ZMM we always
will use XMM.

So my question is why it is done on this way?
why not to choose the maximum VF for equal cost?

-- 
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 35300] New: Add a an option like SpaceBeforeParens but before indexers/square brackets

2017-11-14 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=35300

Bug ID: 35300
   Summary: Add a an option like SpaceBeforeParens but before
indexers/square brackets
   Product: clang
   Version: 5.0
  Hardware: Macintosh
OS: MacOS X
Status: NEW
  Severity: enhancement
  Priority: P
 Component: Formatter
  Assignee: unassignedclangb...@nondot.org
  Reporter: hughbell...@gmail.com
CC: djas...@google.com, kli...@google.com,
llvm-bugs@lists.llvm.org

E.g. The Mono coding guidelines say to put a spsce before '[' in an indexer


int main() {
  static int x[] = {1, 2, 3};

  return x [0];
}

The code above gets formatted to:

int main() {
  static int x[] = {1, 2, 3};

  return x[0];
}

Notice that the space is missing in `x [0]`

Ideally this would not apply to declarations, but I guess this could be
controlled with an enum option

-- 
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 35302] New: missing namespaces when underlying type is a template specialization

2017-11-14 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=35302

Bug ID: 35302
   Summary: missing namespaces when underlying type is a template
specialization
   Product: clang
   Version: 5.0
  Hardware: All
OS: All
Status: NEW
  Severity: normal
  Priority: P
 Component: libclang
  Assignee: unassignedclangb...@nondot.org
  Reporter: istvan.sz...@nng.com
CC: kli...@google.com, llvm-bugs@lists.llvm.org

I'm trying to analyze c++ header files using libclang python bindings.
The following example illustrates the inconsistent namespace handling in type
aliases.

Sample C++ code:

-- BEGIN --
namespace n{
class MyClass{
};
template class MyTemplateClass{
};
}
using namespace n;
using MyClassAlias = MyClass;
using MyTemplateClassAlias = MyTemplateClass;
--  END  --


Sample output generated by libclang python binding:

-- BEGIN --
kind: 'TRANSLATION_UNIT' spelling: 'c:\namespace_bug.h'
  +--kind: 'NAMESPACE' spelling: 'n'
  |  +--kind: 'CLASS_DECL' spelling: 'MyClass'
  |  +--kind: 'CLASS_TEMPLATE' spelling: 'MyTemplateClass'
  | +--kind: 'TEMPLATE_TYPE_PARAMETER' spelling: 'T'
  +--kind: 'USING_DIRECTIVE'
  |  +--kind: 'NAMESPACE_REF' spelling: 'n'
  +--kind: 'TYPE_ALIAS_DECL' spelling: 'MyClassAlias'
underlying_typedef_type.spelling: 'n::MyClass'
  |  +--kind: 'TYPE_REF' spelling: 'class n::MyClass'
  +--kind: 'TYPE_ALIAS_DECL' spelling: 'MyTemplateClassAlias'
underlying_typedef_type.spelling: 'MyTemplateClass'
 +--kind: 'TEMPLATE_REF' spelling: 'MyTemplateClass'
--  END  --

Namespace is missing from the spelling of underlying type in the second type
alias decl.

-- 
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] Issue 4210 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-instcombine: ASSERT: C->getType()->isIntOrIntVectorTy() && Ty->isIntOrIntVectorTy() && "Invalid integ

2017-11-14 Thread monor… via monorail via llvm-bugs

Status: New
Owner: 
CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com,  
llvm-b...@lists.llvm.org, v...@apple.com
Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible  
Engine-libfuzzer Proj-llvm Reported-2017-11-14

Type: Bug

New issue 4210 by monor...@clusterfuzz-external.iam.gserviceaccount.com:  
llvm/llvm-opt-fuzzer--x86_64-instcombine: ASSERT:  
C->getType()->isIntOrIntVectorTy() && Ty->isIntOrIntVectorTy() && "Invalid  
integ

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4210

Detailed report: https://oss-fuzz.com/testcase?key=5258243115843584

Project: llvm
Fuzzer: libFuzzer_llvm_llvm-opt-fuzzer--x86_64-instcombine
Fuzz target binary: llvm-opt-fuzzer--x86_64-instcombine
Job Type: libfuzzer_asan_llvm
Platform Id: linux

Crash Type: ASSERT
Crash Address:
Crash State:
  C->getType()->isIntOrIntVectorTy() && Ty->isIntOrIntVectorTy()  
&& "Invalid integ

  llvm::CastInst::CreateIntegerCast
  llvm::InstCombiner::visitGetElementPtrInst

Sanitizer: address (ASAN)

Regressed:  
https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201711130743:201711140614


Reproducer Testcase:  
https://oss-fuzz.com/download?testcase_id=5258243115843584


Issue filed automatically.

See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for  
more information.


When you fix this bug, please
  * mention the fix revision(s).
  * state whether the bug was a short-lived regression or an old bug in any  
stable releases.

  * add any other useful information.
This information can help downstream consumers.

If you have questions for the OSS-Fuzz team, please file an issue at  
https://github.com/google/oss-fuzz/issues.


--
You received this message because:
  1. You were specifically CC'd on the issue

You may adjust your notification preferences at:
https://bugs.chromium.org/hosting/settings

Reply to this email to add a comment.
___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs


[llvm-bugs] [Bug 17921] [PATCH] armv5te thumb1 target generated UB code mov tGPR, tGPR (should => adds GPR, GPR, #0)

2017-11-14 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=17921

Renato Golin  changed:

   What|Removed |Added

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

--- Comment #4 from Renato Golin  ---
Thanks!

-- 
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 21420] [Meta] Android+Clang platform support

2017-11-14 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=21420
Bug 21420 depends on bug 17921, which changed state.

Bug 17921 Summary: [PATCH] armv5te thumb1 target generated UB code mov tGPR, 
tGPR (should => adds GPR,GPR,#0)
https://bugs.llvm.org/show_bug.cgi?id=17921

   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 35303] New: Merge r315310 into the 5.0 branch : [mips] Partially fix PR34391

2017-11-14 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=35303

Bug ID: 35303
   Summary: Merge r315310 into the 5.0 branch : [mips] Partially
fix PR34391
   Product: new-bugs
   Version: 5.0
  Hardware: PC
OS: All
Status: NEW
  Severity: enhancement
  Priority: P
 Component: new bugs
  Assignee: unassignedb...@nondot.org
  Reporter: simon.dar...@mips.com
CC: llvm-bugs@lists.llvm.org

Fixes an assembly parsing issue building the FreeBSD kernel.

-- 
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 35304] New: include/clang/Tooling/Refactoring/Rename/RenamingAction.h:79]: (performance)

2017-11-14 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=35304

Bug ID: 35304
   Summary: include/clang/Tooling/Refactoring/Rename/RenamingActio
n.h:79]: (performance)
   Product: new-bugs
   Version: trunk
  Hardware: PC
OS: Linux
Status: NEW
  Severity: enhancement
  Priority: P
 Component: new bugs
  Assignee: unassignedb...@nondot.org
  Reporter: dcb...@hotmail.com
CC: llvm-bugs@lists.llvm.org

trunk/llvm/tools/clang/include/clang/Tooling/Refactoring/Rename/RenamingAction.h:79]:
(performance) Function parameter 'NewQualifiedName' should be passed by
reference.

Source code is

  QualifiedRenameRule(const NamedDecl *ND,
  std::string NewQualifiedName)

Maybe better code

  QualifiedRenameRule(const NamedDecl *ND,
  const std::string & NewQualifiedName)

-- 
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 35305] New: Merge r317470 into 5.0.1 branch : [mips] Fix PR35140

2017-11-14 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=35305

Bug ID: 35305
   Summary: Merge r317470 into 5.0.1 branch : [mips] Fix PR35140
   Product: new-bugs
   Version: 5.0
  Hardware: PC
OS: All
Status: NEW
  Severity: enhancement
  Priority: P
 Component: new bugs
  Assignee: unassignedb...@nondot.org
  Reporter: simon.dar...@mips.com
CC: llvm-bugs@lists.llvm.org

Fixes a rust linking issue due to symbol mismatch on the symbol's type.

-- 
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 35306] New: "error in backend: unknown codeview register" while compiling optimized AVX-512 code

2017-11-14 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=35306

Bug ID: 35306
   Summary: "error in backend: unknown codeview register" while
compiling optimized AVX-512 code
   Product: new-bugs
   Version: 5.0
  Hardware: PC
OS: Windows NT
Status: NEW
  Severity: release blocker
  Priority: P
 Component: new bugs
  Assignee: unassignedb...@nondot.org
  Reporter: filip.stru...@intel.com
CC: llvm-bugs@lists.llvm.org

Using llvm/clang 5.0, pre-built 64bit binaries with VS2017

The AVX-512 code (-mavx512f -mavx512bw -mavx512dq) compiles in debug but in
release/optimized build dumps out the following error:

1>CL : fatal error : error in backend: unknown codeview register
1>clang-cl.exe : error : clang frontend command failed with exit code 70 (use
-v to see invocation)
1>clang version 5.0.0 (tags/RELEASE_500/final)
1>Target: x86_64-pc-windows-msvc
1>Thread model: posix
1>InstalledDir: C:\Program Files\LLVM\msbuild-bin
1>clang-cl.exe: note: diagnostic msg: PLEASE submit a bug report to
http://llvm.org/bugs/ and include the crash backtrace, preprocessed source, and
associated run script.
1>clang-cl.exe: note: diagnostic msg:
1>
1>
1>PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT:
1>Preprocessed source(s) and associated run script(s) are located at:
1>clang-cl.exe: note: diagnostic msg:
C:\Users\fstrugar\AppData\Local\Temp\MaskedOcclusionCullingAVX512-18da46.cpp
1>clang-cl.exe: note: diagnostic msg:
C:\Users\fstrugar\AppData\Local\Temp\MaskedOcclusionCullingAVX512-18da46.sh
1>clang-cl.exe: note: diagnostic msg:
1>
1>  


The codebase in question is available publicly at
https://github.com/GameTechDev/MaskedOcclusionCulling - the only modification
needed to trigger the compilation bug is to set USE_AVX512 to 1 in
https://github.com/GameTechDev/MaskedOcclusionCulling/blob/master/MaskedOcclusionCulling.h#L78
and compile the Release_LLVM configuration.

-- 
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 35307] New: Merge r314798 into the 5.0.1 : [mips] Enable spilling and reloading of the dsp register set.

2017-11-14 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=35307

Bug ID: 35307
   Summary: Merge r314798 into the 5.0.1 : [mips] Enable spilling
and reloading of the dsp register set.
   Product: new-bugs
   Version: 5.0
  Hardware: PC
OS: All
Status: NEW
  Severity: enhancement
  Priority: P
 Component: new bugs
  Assignee: unassignedb...@nondot.org
  Reporter: simon.dar...@mips.com
CC: llvm-bugs@lists.llvm.org

-- 
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 34492] [meta] 5.0.1 Release Blockers

2017-11-14 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=34492
Bug 34492 depends on bug 35167, which changed state.

Bug 35167 Summary: Merge r309875 into the 5.0 branch: Move lock acquire/release 
functions in task deque cleanup code
https://bugs.llvm.org/show_bug.cgi?id=35167

   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 35167] Merge r309875 into the 5.0 branch: Move lock acquire/release functions in task deque cleanup code

2017-11-14 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=35167

Tom Stellard  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Fixed By Commit(s)|r309875 |r309875 r318171
 Resolution|--- |FIXED

--- Comment #3 from Tom Stellard  ---
Merged: r318171

-- 
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 35168] Merge r311269 into 5.0 branch: Use va_copy instead of __va_copy to fix building libomp against musl libc

2017-11-14 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=35168

Tom Stellard  changed:

   What|Removed |Added

 Fixed By Commit(s)|r311269 |r311269 r318175
 Status|NEW |RESOLVED
 Resolution|--- |FIXED

--- Comment #3 from Tom Stellard  ---
Merged: r318175

-- 
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 34492] [meta] 5.0.1 Release Blockers

2017-11-14 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=34492
Bug 34492 depends on bug 35168, which changed state.

Bug 35168 Summary: Merge r311269 into 5.0 branch: Use va_copy instead of 
__va_copy to fix building libomp against musl libc
https://bugs.llvm.org/show_bug.cgi?id=35168

   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 35169] Merge r316452 into 5.0 branch: Disable threadprivate data cleanup if runtime is terminating

2017-11-14 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=35169

Tom Stellard  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|NEW |RESOLVED
 Fixed By Commit(s)|r316452 |r316452 r318176

--- Comment #3 from Tom Stellard  ---
Merged: r318176

-- 
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 34492] [meta] 5.0.1 Release Blockers

2017-11-14 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=34492
Bug 34492 depends on bug 35169, which changed state.

Bug 35169 Summary: Merge r316452 into 5.0 branch: Disable threadprivate data 
cleanup if runtime is terminating
https://bugs.llvm.org/show_bug.cgi?id=35169

   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 35171] Merge r317115 into the 5.0 branch: Fix race condition in omp_init_lock

2017-11-14 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=35171

Tom Stellard  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Fixed By Commit(s)|r317115 |r317115 r318178
 Resolution|--- |FIXED

--- Comment #3 from Tom Stellard  ---
Merged: r318178

-- 
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 34492] [meta] 5.0.1 Release Blockers

2017-11-14 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=34492
Bug 34492 depends on bug 35171, which changed state.

Bug 35171 Summary: Merge r317115 into the 5.0 branch: Fix race condition in 
omp_init_lock
https://bugs.llvm.org/show_bug.cgi?id=35171

   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 35289] [SystemZ] different -O0 result with -march=z13

2017-11-14 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=35289

Ulrich Weigand  changed:

   What|Removed |Added

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

--- Comment #4 from Ulrich Weigand  ---
Should be fixed in r318177.

-- 
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 35185] Merge r310522 into the 5.0 branch : [Linker] PR33527 - Linker::LinkOnlyNeeded should import AppendingLinkage globals

2017-11-14 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=35185

Tom Stellard  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Fixed By Commit(s)|r310522 |r310522 r318180
 Resolution|--- |FIXED

--- Comment #4 from Tom Stellard  ---
Merged: r318180

-- 
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 34492] [meta] 5.0.1 Release Blockers

2017-11-14 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=34492
Bug 34492 depends on bug 35185, which changed state.

Bug 35185 Summary: Merge r310522 into the 5.0 branch : [Linker] PR33527 - 
Linker::LinkOnlyNeeded should import AppendingLinkage globals
https://bugs.llvm.org/show_bug.cgi?id=35185

   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 35247] [ThinLTO] Assertion `!Ty->isFunctionTy() && PointerType::isValidElementType(Ty) && "invalid type for global variable"' failed.

2017-11-14 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=35247

Tom Stellard  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Fixed By Commit(s)|r310543 |r310543 r318181
 Status|NEW |RESOLVED

--- Comment #6 from Tom Stellard  ---
Merged: r318181

-- 
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 34492] [meta] 5.0.1 Release Blockers

2017-11-14 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=34492
Bug 34492 depends on bug 35247, which changed state.

Bug 35247 Summary: [ThinLTO] Assertion `!Ty->isFunctionTy() && 
PointerType::isValidElementType(Ty) && "invalid type for global variable"' 
failed.
https://bugs.llvm.org/show_bug.cgi?id=35247

   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 35307] Merge r314798 into the 5.0.1 : [mips] Enable spilling and reloading of the dsp register set.

2017-11-14 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=35307

Tom Stellard  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|NEW |RESOLVED
 Fixed By Commit(s)|r314798 |r314798 r318183

--- Comment #1 from Tom Stellard  ---
Merged: r318183

-- 
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 34492] [meta] 5.0.1 Release Blockers

2017-11-14 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=34492
Bug 34492 depends on bug 35307, which changed state.

Bug 35307 Summary: Merge r314798 into the 5.0.1 : [mips] Enable spilling and 
reloading of the dsp register set.
https://bugs.llvm.org/show_bug.cgi?id=35307

   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 35308] New: Merge r317204+r318172 into the 5.0.1 branch : Enable register scavenging for MSA + simplify test for 5.0.1

2017-11-14 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=35308

Bug ID: 35308
   Summary: Merge r317204+r318172 into the 5.0.1 branch : Enable
register scavenging for MSA + simplify test for 5.0.1
   Product: new-bugs
   Version: 5.0
  Hardware: PC
OS: All
Status: NEW
  Severity: enhancement
  Priority: P
 Component: new bugs
  Assignee: unassignedb...@nondot.org
  Reporter: simon.dar...@mips.com
CC: llvm-bugs@lists.llvm.org

The first patch tweaks the logic determining size of the stack that is likely
to be accessed for MIPS when using MSA and when to enable an emergency spill
slot, the second simplifies the test for the 5.0.1 release.

Fixes an ICE when compiling the LLVM testsuite with MSA and mips64r6.

-- 
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 34859] Isel crash with large constant (csmith)

2017-11-14 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=34859

Ulrich Weigand  changed:

   What|Removed |Added

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

--- Comment #4 from Ulrich Weigand  ---
Should be fixed by r318187.

-- 
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 35281] llvm-objcopy not support armv7e-m

2017-11-14 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=35281

Jake Ehrlich  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|NEW |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 35305] Merge r317470 into 5.0.1 branch : [mips] Fix PR35140

2017-11-14 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=35305

Tom Stellard  changed:

   What|Removed |Added

 Fixed By Commit(s)|r317470 |r317470 r318188
 Resolution|--- |FIXED
 Status|NEW |RESOLVED

--- Comment #1 from Tom Stellard  ---
Merged: r318188

-- 
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 34492] [meta] 5.0.1 Release Blockers

2017-11-14 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=34492
Bug 34492 depends on bug 35305, which changed state.

Bug 35305 Summary: Merge r317470 into 5.0.1 branch : [mips] Fix PR35140
https://bugs.llvm.org/show_bug.cgi?id=35305

   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 35308] Merge r317204+r318172 into the 5.0.1 branch : Enable register scavenging for MSA + simplify test for 5.0.1

2017-11-14 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=35308

Tom Stellard  changed:

   What|Removed |Added

 Fixed By Commit(s)|r317204 r318172 |r317204 r318172 r318191
 Resolution|--- |FIXED
 Status|NEW |RESOLVED

--- Comment #1 from Tom Stellard  ---
Merged: r318191

-- 
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 34492] [meta] 5.0.1 Release Blockers

2017-11-14 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=34492
Bug 34492 depends on bug 35308, which changed state.

Bug 35308 Summary: Merge r317204+r318172 into the 5.0.1 branch : Enable 
register scavenging for MSA + simplify test for 5.0.1
https://bugs.llvm.org/show_bug.cgi?id=35308

   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 34492] [meta] 5.0.1 Release Blockers

2017-11-14 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=34492
Bug 34492 depends on bug 35303, which changed state.

Bug 35303 Summary: Merge r315310 into the 5.0 branch : [mips] Partially fix 
PR34391
https://bugs.llvm.org/show_bug.cgi?id=35303

   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 35303] Merge r315310 into the 5.0 branch : [mips] Partially fix PR34391

2017-11-14 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=35303

Tom Stellard  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Fixed By Commit(s)|r315310 |r315310 r318192
 Status|NEW |RESOLVED

--- Comment #1 from Tom Stellard  ---
Merged: r318192

-- 
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 35310] New: lldb doesn't appear to use abi_tag when resolving names

2017-11-14 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=35310

Bug ID: 35310
   Summary: lldb doesn't appear to use abi_tag when resolving
names
   Product: lldb
   Version: unspecified
  Hardware: PC
OS: Linux
Status: NEW
  Severity: enhancement
  Priority: P
 Component: All Bugs
  Assignee: lldb-...@lists.llvm.org
  Reporter: nelh...@nelhage.com
CC: llvm-bugs@lists.llvm.org

Created attachment 19423
  --> https://bugs.llvm.org/attachment.cgi?id=19423&action=edit
minimal abi_tag test case for lldb

When debugging a C++ program that uses `__attribute__((abi_tag))`, lldb doesn't
seem to be able to look up symbols that have an ABI tag when evaluating
`expression` commands. This manifest most obviously when debugging code linked
against libstdc++, but we can also reproduce with a minimal example without the
STL, 

---8<-- test.cc --8<--

-- 
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 35311] New: Constexpr constructor of templated class does not require member initialization.

2017-11-14 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=35311

Bug ID: 35311
   Summary: Constexpr constructor of templated class does not
require member initialization.
   Product: clang
   Version: unspecified
  Hardware: PC
OS: All
Status: NEW
  Severity: enhancement
  Priority: P
 Component: -New Bugs
  Assignee: unassignedclangb...@nondot.org
  Reporter: chmiel...@int.pl
CC: llvm-bugs@lists.llvm.org

The standard requires that "for the constructor of a class or struct, every
base class sub-object and every non-variant non-static data member must be
initialized."[cpprefence.com]

Clang seems to ignore that requirement if the struct is a template.
This behavior is the same regardless of the version and standard.


Minimal example:

template // commenting out this line generates appropriate errors
struct S{
constexpr S() /*: i(1)*/ {}
int i;
};

constexpr S s;
int main() { return s.i; }

-- 
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 34492] [meta] 5.0.1 Release Blockers

2017-11-14 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=34492
Bug 34492 depends on bug 35250, which changed state.

Bug 35250 Summary: Merge r310905 r310994 into the 5.0 branch : Avoid 
PointerIntPair of constexpr EvalInfo structs
https://bugs.llvm.org/show_bug.cgi?id=35250

   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 35250] Merge r310905 r310994 into the 5.0 branch : Avoid PointerIntPair of constexpr EvalInfo structs

2017-11-14 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=35250

Tom Stellard  changed:

   What|Removed |Added

 Fixed By Commit(s)|r310905 r310994 |r310905 r310994 r318225
 Resolution|--- |FIXED
 Status|NEW |RESOLVED

--- Comment #4 from Tom Stellard  ---
Merged: r318225

-- 
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] Issue 4214 in oss-fuzz: llvm/llvm-dwarfdump-fuzzer: ASSERT: getAddressSize() == DebugLineData.getAddressSize() && "Line table header and dat

2017-11-14 Thread monor… via monorail via llvm-bugs

Status: New
Owner: 
CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com,  
llvm-b...@lists.llvm.org, v...@apple.com
Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible  
Engine-libfuzzer Proj-llvm Reported-2017-11-15

Type: Bug

New issue 4214 by monor...@clusterfuzz-external.iam.gserviceaccount.com:  
llvm/llvm-dwarfdump-fuzzer: ASSERT: getAddressSize() ==  
DebugLineData.getAddressSize() && "Line table header and dat

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4214

Detailed report: https://oss-fuzz.com/testcase?key=5107633510940672

Project: llvm
Fuzzer: libFuzzer_llvm_llvm-dwarfdump-fuzzer
Fuzz target binary: llvm-dwarfdump-fuzzer
Job Type: libfuzzer_asan_llvm
Platform Id: linux

Crash Type: ASSERT
Crash Address:
Crash State:
  getAddressSize() == DebugLineData.getAddressSize() && "Line table header  
and dat

  llvm::DWARFDebugLine::Prologue::parse
  llvm::DWARFContext::dump

Sanitizer: address (ASAN)

Regressed:  
https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201708280446:201708291805


Reproducer Testcase:  
https://oss-fuzz.com/download?testcase_id=5107633510940672


Issue filed automatically.

See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for  
more information.


When you fix this bug, please
  * mention the fix revision(s).
  * state whether the bug was a short-lived regression or an old bug in any  
stable releases.

  * add any other useful information.
This information can help downstream consumers.

If you have questions for the OSS-Fuzz team, please file an issue at  
https://github.com/google/oss-fuzz/issues.


--
You received this message because:
  1. You were specifically CC'd on the issue

You may adjust your notification preferences at:
https://bugs.chromium.org/hosting/settings

Reply to this email to add a comment.
___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs


[llvm-bugs] Issue 4215 in oss-fuzz: llvm: Stack-overflow in clang::DiagnosticIDs::ProcessDiag

2017-11-14 Thread monor… via monorail via llvm-bugs

Status: New
Owner: 
CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com,  
llvm-b...@lists.llvm.org, v...@apple.com
Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible  
Engine-libfuzzer Proj-llvm Reported-2017-11-15

Type: Bug

New issue 4215 by monor...@clusterfuzz-external.iam.gserviceaccount.com:  
llvm: Stack-overflow in clang::DiagnosticIDs::ProcessDiag

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4215

Detailed report: https://oss-fuzz.com/testcase?key=5181080404492288

Project: llvm
Fuzzer: libFuzzer_llvm_clang-fuzzer
Job Type: libfuzzer_asan_llvm
Platform Id: linux

Crash Type: Stack-overflow
Crash Address: 0x7ffee5f11fe0
Crash State:
  clang::DiagnosticIDs::ProcessDiag
  clang::DiagnosticsEngine::EmitCurrentDiagnostic
  clang::Lexer::LexTokenInternal

Sanitizer: address (ASAN)

Regressed:  
https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201711140614:201711141648


Reproducer Testcase:  
https://oss-fuzz.com/download?testcase_id=5181080404492288


Issue filed automatically.

See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for  
more information.


When you fix this bug, please
  * mention the fix revision(s).
  * state whether the bug was a short-lived regression or an old bug in any  
stable releases.

  * add any other useful information.
This information can help downstream consumers.

If you have questions for the OSS-Fuzz team, please file an issue at  
https://github.com/google/oss-fuzz/issues.


--
You received this message because:
  1. You were specifically CC'd on the issue

You may adjust your notification preferences at:
https://bugs.chromium.org/hosting/settings

Reply to this email to add a comment.
___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs


[llvm-bugs] [Bug 35181] Merge r315464 into the 5.0 branch: Fix PR34916: Crash on mixing taskloop|tasks directives.

2017-11-14 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=35181

Tom Stellard  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Fixed By Commit(s)|r315464 |r315464 r318233
 Resolution|--- |FIXED

--- Comment #5 from Tom Stellard  ---
Merged: r318233

-- 
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 34492] [meta] 5.0.1 Release Blockers

2017-11-14 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=34492
Bug 34492 depends on bug 35181, which changed state.

Bug 35181 Summary: Merge r315464 into the 5.0 branch: Fix PR34916: Crash on 
mixing taskloop|tasks directives.
https://bugs.llvm.org/show_bug.cgi?id=35181

   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 35312] New: Merge r318207 into the 5.0.1 branch: Reland "[mips][mt][6/7] Add support for mftr, mttr instructions."

2017-11-14 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=35312

Bug ID: 35312
   Summary: Merge r318207 into the 5.0.1 branch: Reland
"[mips][mt][6/7] Add support for mftr, mttr
instructions."
   Product: new-bugs
   Version: 5.0
  Hardware: PC
OS: All
Status: NEW
  Severity: enhancement
  Priority: P
 Component: new bugs
  Assignee: unassignedb...@nondot.org
  Reporter: simon.dar...@mips.com
CC: llvm-bugs@lists.llvm.org

This patch finishes support for the MIPS MT ASE (Optional ISA extension).

-- 
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 34492] [meta] 5.0.1 Release Blockers

2017-11-14 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=34492
Bug 34492 depends on bug 35186, which changed state.

Bug 35186 Summary: Merge r313776 into the 5.0 branch
https://bugs.llvm.org/show_bug.cgi?id=35186

   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 35186] Merge r313776 into the 5.0 branch

2017-11-14 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=35186

Tom Stellard  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Fixed By Commit(s)|r313776 |r313776 r318236
 Resolution|--- |FIXED

--- Comment #3 from Tom Stellard  ---
Merged: r318236

-- 
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 35210] crash from LoopRotate

2017-11-14 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=35210

Craig Topper  changed:

   What|Removed |Added

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

--- Comment #16 from Craig Topper  ---
Fixed the underlying bug in r318237

-- 
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] Issue 4217 in oss-fuzz: llvm: Stack-overflow in clang::DiagnosticBuilder::AddString

2017-11-14 Thread monor… via monorail via llvm-bugs

Status: New
Owner: 
CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com,  
llvm-b...@lists.llvm.org, v...@apple.com
Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible  
Engine-libfuzzer Proj-llvm Reported-2017-11-15

Type: Bug

New issue 4217 by monor...@clusterfuzz-external.iam.gserviceaccount.com:  
llvm: Stack-overflow in clang::DiagnosticBuilder::AddString

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4217

Detailed report: https://oss-fuzz.com/testcase?key=6244564772847616

Project: llvm
Fuzzer: libFuzzer_llvm_clang-fuzzer
Job Type: libfuzzer_asan_llvm
Platform Id: linux

Crash Type: Stack-overflow
Crash Address: 0x7ffc2d773e58
Crash State:
  clang::DiagnosticBuilder::AddString
  clang::NumericLiteralParser::NumericLiteralParser
  clang::Sema::ActOnNumericConstant

Sanitizer: address (ASAN)

Regressed:  
https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201711140614:201711141648


Reproducer Testcase:  
https://oss-fuzz.com/download?testcase_id=6244564772847616


Issue filed automatically.

See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for  
more information.


When you fix this bug, please
  * mention the fix revision(s).
  * state whether the bug was a short-lived regression or an old bug in any  
stable releases.

  * add any other useful information.
This information can help downstream consumers.

If you have questions for the OSS-Fuzz team, please file an issue at  
https://github.com/google/oss-fuzz/issues.


--
You received this message because:
  1. You were specifically CC'd on the issue

You may adjust your notification preferences at:
https://bugs.chromium.org/hosting/settings

Reply to this email to add a comment.
___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs


[llvm-bugs] [Bug 35313] New: Enhancement: Implement MOV32 #imm on arm.

2017-11-14 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=35313

Bug ID: 35313
   Summary: Enhancement:  Implement MOV32 #imm on arm.
   Product: libraries
   Version: trunk
  Hardware: PC
OS: All
Status: NEW
  Severity: enhancement
  Priority: P
 Component: Backend: ARM
  Assignee: unassignedb...@nondot.org
  Reporter: codeman.consult...@gmail.com
CC: llvm-bugs@lists.llvm.org

The ARM documents list MOV32 as an alias for MOVW/MOVT which accepts a 32 bit
immediate.  Since this is supported by the arm assembler, it seems reasonable
(and relatively easy) to support it on this end.  We get the bonus of more
readable MOVW/MOVT loads of addresses and users get simpler assembly.   It
looks like AArch64 does something like this already with the 4 instruction 64
bit MOV grouping.

-- 
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 35214] clang/master: Assertion failed: (getType(Base)->isPointerType() || getType(Base)->isArrayType()), function addUnsizedArray

2017-11-14 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=35214

Richard Smith  changed:

   What|Removed |Added

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

--- Comment #5 from Richard Smith  ---
Fixed in r318258.

-- 
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] Issue 4218 in oss-fuzz: llvm: Stack-overflow in UnqualUsingDirectiveSet::addUsingDirectives

2017-11-14 Thread monor… via monorail via llvm-bugs

Status: New
Owner: 
CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com,  
llvm-b...@lists.llvm.org, v...@apple.com
Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible  
Engine-libfuzzer Proj-llvm Reported-2017-11-15

Type: Bug

New issue 4218 by monor...@clusterfuzz-external.iam.gserviceaccount.com:  
llvm: Stack-overflow in UnqualUsingDirectiveSet::addUsingDirectives

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4218

Detailed report: https://oss-fuzz.com/testcase?key=6724214305325056

Project: llvm
Fuzzer: libFuzzer_llvm_clang-fuzzer
Job Type: libfuzzer_asan_llvm
Platform Id: linux

Crash Type: Stack-overflow
Crash Address: 0x7ffcfe850fc0
Crash State:
  UnqualUsingDirectiveSet::addUsingDirectives
  UnqualUsingDirectiveSet::visitScopeChain
  clang::Sema::CppLookupName

Sanitizer: address (ASAN)

Regressed:  
https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201711140614:201711141648


Reproducer Testcase:  
https://oss-fuzz.com/download?testcase_id=6724214305325056


Issue filed automatically.

See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for  
more information.


When you fix this bug, please
  * mention the fix revision(s).
  * state whether the bug was a short-lived regression or an old bug in any  
stable releases.

  * add any other useful information.
This information can help downstream consumers.

If you have questions for the OSS-Fuzz team, please file an issue at  
https://github.com/google/oss-fuzz/issues.


--
You received this message because:
  1. You were specifically CC'd on the issue

You may adjust your notification preferences at:
https://bugs.chromium.org/hosting/settings

Reply to this email to add a comment.
___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs


[llvm-bugs] [Bug 15481] noexcept should check whether the expression is a constant expression

2017-11-14 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=15481

Richard Smith  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |INVALID

--- Comment #5 from Richard Smith  ---
Conclusion from CWG discussion: we're going to keep this as-is. "noexcept" has
no special rule for constant expressions.

It turns out this is actually essential for proper library functionality: eg,
if noexcept tries evaluating its operand, then (for example)
is_nothrow_swappable is broken by making std::swap constexpr, because
std::swap then often ends up getting instantiated before T is complete.

As a result of that, I'm also going to consider this change as an effective DR
against C++11 and C++14... but I'm open to reconsidering if we see many user
complaints.

-- 
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 35314] New: stack overflow in debug info for union debug info

2017-11-14 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=35314

Bug ID: 35314
   Summary: stack overflow in debug info for union debug info
   Product: libraries
   Version: 5.0
  Hardware: All
OS: All
Status: NEW
  Severity: normal
  Priority: P
 Component: DebugInfo
  Assignee: unassignedb...@nondot.org
  Reporter: superjo...@gmail.com
CC: llvm-bugs@lists.llvm.org

Created attachment 19424
  --> https://bugs.llvm.org/attachment.cgi?id=19424&action=edit
test.ll

With llvm 5.0.0, `clang -c test.ll` causes a stack overflow and then segfault.

-- 
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 34958] Clang produces broken debug info: inlinable function call in a function with debug info must have a !dbg location

2017-11-14 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=34958

Matt Arsenault  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 Status|NEW |RESOLVED

--- Comment #3 from Matt Arsenault  ---
Seems to work now on trunk for me as well.

-- 
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