[llvm-bugs] [Bug 40475] New: Incorrect interaction of decltype with operator<

2019-01-26 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=40475

Bug ID: 40475
   Summary: Incorrect interaction of decltype with operator<<
   Product: clang
   Version: unspecified
  Hardware: Macintosh
OS: MacOS X
Status: NEW
  Severity: normal
  Priority: P
 Component: C++
  Assignee: unassignedclangb...@nondot.org
  Reporter: oliver.ros...@googlemail.com
CC: blitzrak...@gmail.com, dgre...@apple.com,
erik.pilking...@gmail.com, llvm-bugs@lists.llvm.org,
richard-l...@metafoo.co.uk

I'm running clang-1000.11.45.5 on my mac. To my bafflement, the following
snippet compiles and runs, producing "Hello, world!":

struct foo
{
};

decltype(std::stringstream{} << foo{}) f{"Hello, world!"};

//f << foo{};

std::cout << f.str() << '\n';

Reinstating the commented line does at least give the expected compilation
error since no appropriate operator<< exists.

As far as I can tell, the problem seems specific to mac.

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


[llvm-bugs] [Bug 40476] New: [X86][SSE] Recognise out of range shift behaviour

2019-01-26 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=40476

Bug ID: 40476
   Summary: [X86][SSE] Recognise out of range shift behaviour
   Product: libraries
   Version: trunk
  Hardware: PC
OS: Windows NT
Status: NEW
  Severity: enhancement
  Priority: P
 Component: Backend: X86
  Assignee: unassignedb...@nondot.org
  Reporter: llvm-...@redking.me.uk
CC: craig.top...@gmail.com, llvm-bugs@lists.llvm.org,
llvm-...@redking.me.uk, spatel+l...@rotateright.com

As discussed on D46946, we should recognise when we're trying to handle/clamp
out of range vector shift amounts and make use of the SSE/AVX2 behaviours
instead.

For generic shifts this means we'd need to explicitly replace them with the x86
shift intrinsics.

https://godbolt.org/z/RSDKOh

The "uniform" SSE2 shifts are trickier but would benefit from the same
optimization.

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


[llvm-bugs] [Bug 40477] New: Packages without version number no longer map to snapshot

2019-01-26 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=40477

Bug ID: 40477
   Summary: Packages without version number no longer map to
snapshot
   Product: Packaging
   Version: unspecified
  Hardware: All
OS: Linux
Status: NEW
  Severity: normal
  Priority: P
 Component: deb packages
  Assignee: unassignedb...@nondot.org
  Reporter: kim.gras...@gmail.com
CC: llvm-bugs@lists.llvm.org

We use Travis for CI builds, and rely on their llvm-toolchain-trusty source.

I'm not entirely sure how that's wired, but ever since the LLVM/Clang 8 branch
was made and trunk switched to 9, installing e.g. `clang` no longer works:

https://travis-ci.org/include-what-you-use/include-what-you-use/builds/483638279?utm_source=github_status&utm_medium=notification

So it looks like something needs to be done to make the default packages point
back to the -snapshot builds for trunk/master.

Thanks for any ideas!

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


[llvm-bugs] [Bug 40478] New: [WebAssembly] Define the __wasi__ target macro

2019-01-26 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=40478

Bug ID: 40478
   Summary: [WebAssembly] Define the __wasi__ target macro
   Product: clang
   Version: unspecified
  Hardware: All
OS: other
Status: NEW
  Severity: release blocker
  Priority: P
 Component: Frontend
  Assignee: unassignedclangb...@nondot.org
  Reporter: dan433...@gmail.com
CC: ahee...@gmail.com, dsch...@google.com,
llvm-bugs@lists.llvm.org, neeil...@live.com,
richard-l...@metafoo.co.uk, s...@chromium.org

Please merge r352099 and r352105 to the release branch.

This adds the __wasi__ target OS macro needed by the new wasm32-unknown-wasi
target triple. The Triple support is already in the tree; this just adds a
predefined macro for it. 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
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs


[llvm-bugs] [Bug 40479] New: clang crashes on valid code at -O3 with debugging enabled: fatal error: error in backend: Broken function found, compilation aborted!

2019-01-26 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=40479

Bug ID: 40479
   Summary: clang crashes on valid code at -O3 with debugging
enabled: fatal error: error in backend: Broken
function found, compilation aborted!
   Product: new-bugs
   Version: trunk
  Hardware: PC
OS: Linux
Status: NEW
  Severity: normal
  Priority: P
 Component: new bugs
  Assignee: unassignedb...@nondot.org
  Reporter: s...@cs.ucdavis.edu
CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org

Tested with trunk revision 352264, and looks like a recent regression. 

$ cltrunk -v
clang version 9.0.0 (http://llvm.org/git/clang.git
8a558a52a96fc5411834e6e015219513a9986bdc) (http://llvm.org/git/llvm.git
6033f8c97abfccb3d9367694f62570ea980ccd81)
Target: x86_64-unknown-linux-gnu
Thread model: posix
InstalledDir: /home/su/bin
Found candidate GCC installation: /usr/lib/gcc/i686-linux-gnu/5
Found candidate GCC installation: /usr/lib/gcc/i686-linux-gnu/5.4.0
Found candidate GCC installation: /usr/lib/gcc/i686-linux-gnu/6
Found candidate GCC installation: /usr/lib/gcc/i686-linux-gnu/6.0.0
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.4
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.4.7
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.6
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.6.4
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.7
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.7.4
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.8
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.8.5
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.9
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.9.3
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/5
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/5.4.0
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/6
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/6.0.0
Selected GCC installation: /usr/lib/gcc/x86_64-linux-gnu/5.4.0
Candidate multilib: .;@m64
Candidate multilib: 32;@m32
Candidate multilib: x32;@mx32
Selected multilib: .;@m64
$ 
$ cltrunk -O3 -g small.c
llvm.dbg.label intrinsic requires a !dbg attachment
  call void @llvm.dbg.label(metadata !26) #3
label %L1.outer.us.preheader.i.split.us
i32 ()* @main
llvm.dbg.label intrinsic requires a !dbg attachment
  call void @llvm.dbg.label(metadata !27) #3
label %L1.outer.us.preheader.i.split.us
i32 ()* @main
llvm.dbg.label intrinsic requires a !dbg attachment
  call void @llvm.dbg.label(metadata !26) #3
label %L1.outer.us.preheader.i.split.us
i32 ()* @main
llvm.dbg.label intrinsic requires a !dbg attachment
  call void @llvm.dbg.label(metadata !27) #3
label %L1.outer.us.preheader.i.split.us
i32 ()* @main
in function main
fatal error: error in backend: Broken function found, compilation aborted!
clang-8: error: clang frontend command failed with exit code 70 (use -v to see
invocation)
clang version 9.0.0 (http://llvm.org/git/clang.git
8a558a52a96fc5411834e6e015219513a9986bdc) (http://llvm.org/git/llvm.git
6033f8c97abfccb3d9367694f62570ea980ccd81)
Target: x86_64-unknown-linux-gnu
Thread model: posix
InstalledDir: /home/su/bin
clang-8: note: diagnostic msg: PLEASE submit a bug report to
https://bugs.llvm.org/ and include the crash backtrace, preprocessed source,
and associated run script.
clang-8: note: diagnostic msg: 


PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT:
Preprocessed source(s) and associated run script(s) are located at:
clang-8: note: diagnostic msg: /tmp/small-bc8f7f.c
clang-8: note: diagnostic msg: /tmp/small-bc8f7f.sh
clang-8: note: diagnostic msg: 


$ 





int printf (const char *, ...);

struct
{
  int a:10;
} b;

int c, d;

void e ()
{
  int f, g;
  short h;
  g = c;
  h = f = ~g;
L1:
  b.a = (~g || d) - 1;
  if (f)
goto L1;
L2:
  if (h)
{
  g = h;
  goto L1;
}
  if (c)
{
  printf ("%d\n", c);
  goto L2;
}
}

int main ()
{
  if (c)
e ();
  return 0;
}

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


[llvm-bugs] [Bug 40289] X86: Signed Overflowing Multiplication incorrect codegen on 32-bit Windows

2019-01-26 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=40289

Simon Pilgrim  changed:

   What|Removed |Added

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

--- Comment #3 from Simon Pilgrim  ---
Fixed in rL351146

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


[llvm-bugs] [Bug 40480] New: clang-format gets confused with custom for each macro

2019-01-26 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=40480

Bug ID: 40480
   Summary: clang-format gets confused with custom for each macro
   Product: clang
   Version: 7.0
  Hardware: PC
OS: Linux
Status: NEW
  Severity: enhancement
  Priority: P
 Component: Formatter
  Assignee: unassignedclangb...@nondot.org
  Reporter: patrick.peliss...@gmail.com
CC: djas...@google.com, kli...@google.com,
llvm-bugs@lists.llvm.org

For the test case below that uses a for each macro M_EACH provided by some
library to iterate over a container:

int f(aint_t a)
{
  int s = 0;
  for M_EACH(item, a, aint_t) {
  int z = *item;
  s += z;
  }
  return s;
}

is transformed into:

int f(aint_t a) {
  int s = 0;
  for
M_EACH(item, a, aint_t) {
  int z = *item;
  s += z;
}
  return s;
}

There is no option to prevent the end of line after the for and before the
M_EACH macro.

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


[llvm-bugs] [Bug 40481] New: lld: cannot link library by passing absolute path

2019-01-26 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=40481

Bug ID: 40481
   Summary: lld: cannot link library by passing absolute path
   Product: lld
   Version: unspecified
  Hardware: PC
OS: Linux
Status: NEW
  Severity: enhancement
  Priority: P
 Component: All Bugs
  Assignee: unassignedb...@nondot.org
  Reporter: m...@milianw.de
CC: llvm-bugs@lists.llvm.org, peter.sm...@linaro.org

$ cat test.cpp
#include 
#include 

int main(int argc, char** argv)
{
QCoreApplication app(argc, argv);
QTimer::singleShot(1000, [&app](){ app.quit(); });
return app.exec();
}

$ ld --version
GNU gold (GNU Binutils 2.31.1) 1.16
...

$ g++ -g -O0 -I/usr/include/qt -I/usr/include/qt/QtCore -fPIC
-l/usr/lib/libQt5Core.so test.cpp
# this works just fine

# now I change my ld symlink and retry with ld:

$ ld --version
LLD 7.0.1 (compatible with GNU linkers)

$ g++ -g -O0 -I/usr/include/qt -I/usr/include/qt/QtCore -fPIC
-l/usr/lib/libQt5Core.so test.cpp
ld: error: unable to find library -l/usr/lib/libQt5Core.so
collect2: error: ld returned 1 exit status

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


[llvm-bugs] [Bug 40482] New: lld creates bogus dwarf info

2019-01-26 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=40482

Bug ID: 40482
   Summary: lld creates bogus dwarf info
   Product: lld
   Version: unspecified
  Hardware: PC
OS: Linux
Status: NEW
  Severity: enhancement
  Priority: P
 Component: All Bugs
  Assignee: unassignedb...@nondot.org
  Reporter: m...@milianw.de
CC: llvm-bugs@lists.llvm.org, peter.sm...@linaro.org

$ g++ --version
g++ (GCC) 8.2.1 20181127

$ ld --version
LLD 7.0.1 (compatible with GNU linkers)

$ gdb --version
GNU gdb (GDB) 8.2.1

I just tried to switch to ld.lld from ld.gold for performance reasons, but hit
a road block: Apparently the DWARF emitted into the final executable or library
is bogus and leads to issues when trying to load it then in consumers like gdb,
valgrind, bloaty, ...

Here are some examples from a single KDE projects (ki18n). Note that I was so
far not able to reproduce this in a simplified standalone example.

Reading symbols from bin/libKF5I18n.so...Dwarf Error: bad offset
(0xcc0826980004) in compilation unit header (offset 0x6fbe2 + 6) [in module
/home/milian/projects/kf5/build-dbg/frameworks/ki18n/bin/libKF5I18n.so.5.54.0]

Reading symbols from ktranscript.so...Dwarf Error: wrong version in compilation
unit header (is 422, should be 2, 3, 4 or 5) [in module
/home/milian/projects/kf5/build-dbg/frameworks/ki18n/bin/ktranscript.so]

Reading symbols from ki18n-ktranscripttest...Dwarf Error: wrong version in
compilation unit header (is 1024, should be 2, 3, 4 or 5) [in module
/home/milian/projects/kf5/build-dbg/frameworks/ki18n/bin/ki18n-ktranscripttest]

I have seen at least one more variation of the version header issue (version
514).

When I instead link with ld.gold, none of these issues show up.

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


[llvm-bugs] [Bug 40483] New: [X86] Failure to merge ISD::SUB(x, y) and X86ISD::SUB(x.y)

2019-01-26 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=40483

Bug ID: 40483
   Summary: [X86] Failure to merge ISD::SUB(x,y) and
X86ISD::SUB(x.y)
   Product: libraries
   Version: trunk
  Hardware: PC
OS: Windows NT
Status: NEW
  Severity: enhancement
  Priority: P
 Component: Backend: X86
  Assignee: unassignedb...@nondot.org
  Reporter: llvm-...@redking.me.uk
CC: craig.top...@gmail.com, llvm-bugs@lists.llvm.org,
llvm-...@redking.me.uk, spatel+l...@rotateright.com

We sometimes fail to recognise that ISD::SUB(x,y) and X86ISD::SUB(x,y) can be
represented by the X86ISD::SUB(x,y).

https://godbolt.org/z/-RFU9J

#include 

using u64 = unsigned long long;

u64 test_sub1(u64 *p, u64 x) {
  u64 r = *p - x;
  _subborrow_u64(0, *p, x, p);
  return *p - r; // zero
}

u64 test_sub2(u64 *p, u64 x) {
  u64 r = *p - x;
  _subborrow_u64(0, *p, x, p);
  return r - *p; // zero
}

_Z9test_sub1Pyy:
movq(%rdi), %rcx
movq%rcx, %rax
subq%rsi, %rax
movq%rax, (%rdi)
subq%rcx, %rsi
addq%rsi, %rax
retq
_Z9test_sub2Pyy:
subq%rsi, (%rdi)
xorl%eax, %eax
retq

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


[llvm-bugs] Issue 12715 in oss-fuzz: llvm/clang-fuzzer: ASSERT: isa(Val) && "cast() argument of incompatible type!"

2019-01-26 Thread ClusterFuzz-External via monorail via llvm-bugs

Status: New
Owner: 
CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com,  
igm...@gmail.com, eney...@google.com, llvm-b...@lists.llvm.org,  
j...@chromium.org, v...@apple.com, mitchphi...@outlook.com,  
xpl...@gmail.com, akils...@apple.com
Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible  
Engine-libfuzzer Proj-llvm Reported-2019-01-27

Type: Bug

New issue 12715 by ClusterFuzz-External: llvm/clang-fuzzer: ASSERT:  
isa(Val) && "cast() argument of incompatible type!"

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

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

Project: llvm
Fuzzer: libFuzzer_llvm_clang-fuzzer
Fuzz target binary: clang-fuzzer
Job Type: libfuzzer_asan_llvm
Platform Id: linux

Crash Type: ASSERT
Crash Address:
Crash State:
  isa(Val) && "cast() argument of incompatible type!"
  clang::Sema::tryCaptureVariable
  clang::Sema::BuildDeclarationNameExpr

Sanitizer: address (ASAN)

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


Issue filed automatically.

See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for  
instructions to reproduce this bug locally.


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 need to contact the OSS-Fuzz team with a question, concern, or any  
other feedback, 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
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs


[llvm-bugs] [Bug 31719] LLVM maintain useless state when using adc

2019-01-26 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=31719

deadalnix  changed:

   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
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs


[llvm-bugs] [Bug 40484] New: relocation R_X86_64_PC32 against undefined hidden symbol error when building a C++ shared library that links against static boost libraries

2019-01-26 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=40484

Bug ID: 40484
   Summary: relocation R_X86_64_PC32 against undefined hidden
symbol error when building a C++ shared library that
links against static boost libraries
   Product: clang
   Version: 7.0
  Hardware: PC
OS: Linux
Status: NEW
  Severity: normal
  Priority: P
 Component: C++
  Assignee: unassignedclangb...@nondot.org
  Reporter: bge...@unscrambl.com
CC: blitzrak...@gmail.com, dgre...@apple.com,
erik.pilking...@gmail.com, llvm-bugs@lists.llvm.org,
richard-l...@metafoo.co.uk

We are getting a 'relocation R_X86_64_PC32 against undefined hidden symbol
error' when building a C++ shared library that links against static boost
libraries (built with -fPIC). I have a reproduction below. There a few details
that may help:

- The error only happens with clang (I tried 6 and 7) but not with gcc
- It does not matter whether boost is built with clang or gcc, so I believe the
problem is related to the compilation of the object file that is being made
into a shared library
- The problem is somewhat related to a class called 'wrapexcept' in boost, as
it is always a symbol related to this class that is causing a problem. The
symbol is a 'construction vtable', so there is multi-inheritance and templates
involved and certainly this is related to the fact that boost is built with
-fvisibility=hidden -fvisibility-inlines-hidden. 
- A potentially related earlier bug is:
https://bugs.llvm.org/show_bug.cgi?id=8713

Here is a reproduction:

I have a very simple test.cpp file:

=
#include 

int test()
{
boost::regex const regex("a");
return 0;
}
=

clang++-7 -fPIC -I $BOOST_PATH/include -c test.cpp

clang++-7 -fPIC -shared -o libtest.so test.o $BOOST_PATH//lib/libboost_regex.a

/usr/bin/ld: /opt/boost-1.69.0/lib/libboost_regex.a(regex.o): relocation
R_X86_64_PC32 against undefined hidden symbol
`_ZTCN5boost10wrapexceptISt13runtime_errorEE0_NS_16exception_detail10clone_implINS3_19error_info_injectorIS1_'
can not be used when making a shared object
/usr/bin/ld: final link failed: Bad value

c++filt
_ZTCN5boost10wrapexceptISt13runtime_errorEE0_NS_16exception_detail10clone_implINS3_19error_info_injectorIS1_
gives:

construction vtable for
boost::exception_detail::clone_impl
>-in-boost::wrapexcept

We are using Boost 1.69 with only static libaries. Here is how we built it:

./bootstrap.sh
./b2 -d+2 -a install -j 16 -prefix=$BOOST_PATH link=static cxxflags="-fPIC"
variant=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
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs


[llvm-bugs] [Bug 39565] Foundation website SSL connections are not working.

2019-01-26 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=39565
Bug 39565 depends on bug 39309, which changed state.

Bug 39309 Summary: foundation page link goes to 
"http://foundation.llvm.org/documents/"; rather than 
"http://llvm.org/foundation/documents/";
https://bugs.llvm.org/show_bug.cgi?id=39309

   What|Removed |Added

 Status|CONFIRMED   |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
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs


[llvm-bugs] [Bug 39309] foundation page link goes to "http://foundation.llvm.org/documents/" rather than "http://llvm.org/foundation/documents/"

2019-01-26 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=39309

Mike Edwards  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED

--- Comment #1 from Mike Edwards  ---
I have made the appropriate changes to the apache configs (included below) to
get the redirects to work correctly.

Currently we are going to land all of the Foundation traffic on
llvm.org/foundation.  Not sure if this will be the ultimate destination as we
seem to be moving towards sub-domains for all of the different llvm resources. 
For now though, everything lives on llvm.org under a path.

The current fix is to add these two lines to the two foundation apache2 conf
files:

Redirect temp /foundation/ https://foundation.llvm.org/
Redirect temp / https://llvm.org/foundation/

The files in question are:
/etc/apache2/sites-available/foundation.conf
/etc/apache2/sites-available/foundation-le-ssl.conf

I have verified this is working by clicking the previous 404 links below and
they now return 200's with the expected page content.

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


[llvm-bugs] [Bug 39565] Foundation website SSL connections are not working.

2019-01-26 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=39565

Mike Edwards  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED

--- Comment #1 from Mike Edwards  ---
I have fixed the errors associated with the configuration of the foundations
website.  See the fix in 39309.

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


[llvm-bugs] [Bug 40395] __uuidof at a template argument causes infinite template instantiation

2019-01-26 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=40395

Bill Wendling  changed:

   What|Removed |Added

 Status|CONFIRMED   |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
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs


[llvm-bugs] [Bug 2722] Forward links from old documention

2019-01-26 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=2722

Mike Edwards  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 CC||m...@sqlby.me
 Status|NEW |RESOLVED

--- Comment #2 from Mike Edwards  ---
So trying to google the below example brought me to an LLVM 7.0 nightly test
documentation page.  I think this has been resolved for some time now.  If I'm
incorrect please reopen and I'm happy to have another look.

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


[llvm-bugs] [Bug 12235] LLVM online demo exposes server files

2019-01-26 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=12235

Mike Edwards  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 CC||m...@sqlby.me
 Resolution|--- |FIXED

--- Comment #1 from Mike Edwards  ---
The llvm demo page has been disabled for some time now.  I believe either Anton
or Tanya took care of this several years ago.  I'm marking this resolved.  If
anyone finds to the contrary please reopen and I'll be happy to have another
look.

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


[llvm-bugs] [Bug 15163] ViewVC links taking me to wrong part of repository

2019-01-26 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=15163

Mike Edwards  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 Status|NEW |RESOLVED
 CC||m...@sqlby.me

--- Comment #1 from Mike Edwards  ---
Looks like this is working now.  I assume this was probably fixed when we moved
to AWS as we fixed quite a few things with links and whatnot.  I'm sure credit
belongs to Anton or Tanya or one of several other people.  I didn't fix
anything, I just confirmed the links now work as they are expected to.

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


[llvm-bugs] [Bug 31219] Private links at http://clang.llvm.org/cxx_status.html#cxx17

2019-01-26 Thread via llvm-bugs
https://bugs.llvm.org/show_bug.cgi?id=31219

Mike Edwards  changed:

   What|Removed |Added

 CC||m...@sqlby.me
 Status|NEW |RESOLVED
 Resolution|--- |WORKSFORME

--- Comment #3 from Mike Edwards  ---
The private links appear to be public now and the broken link has been repaired
by someone long before I arrived here.  This all LGTM 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
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs