[llvm-bugs] [Bug 40190] New: When rewriting the `From:` email header, need to add real sender to `Reply-To:` header.
https://bugs.llvm.org/show_bug.cgi?id=40190 Bug ID: 40190 Summary: When rewriting the `From:` email header, need to add real sender to `Reply-To:` header. Product: Phabricator Version: unspecified Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: All Bugs Assignee: unassignedb...@nondot.org Reporter: chandl...@gmail.com CC: llvm-bugs@lists.llvm.org When Phabricator is sending email on my behalf, it will rewrite the `From:` header in order to avoid DMARC issues. This is good (if a frustrating necessity). However, unlike the mailing lists, Phab does not take the original contents of the `From:` header and put them into the `Reply-To:` header. This is bad for many reasons. First, it makes it hard (impossible?) to reliably detect what email address is associated with the sender. Second, replies may fail to include the sender which is surprising. Here is the doubly re-written `From:` header from one such phab update: ``` From: Chandler Carruth via Phabricator via llvm-commits ``` And here is the `Reply-To:` header showing the original `Reply-To:` added by Phab to capture responses, and the list has added Phab's `From:` into it, but we have lost the original author email: ``` Reply-To: reviews+d56162+public+e080bc19d9bb3...@reviews.llvm.org, Chandler Carruth via Phabricator ``` -- 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 40191] New: Can 'omp cancel parallel' really be not directly nested within 'omp parallel'?
https://bugs.llvm.org/show_bug.cgi?id=40191
Bug ID: 40191
Summary: Can 'omp cancel parallel' really be not directly
nested within 'omp parallel'?
Product: OpenMP
Version: unspecified
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: Clang Compiler Support
Assignee: unassignedclangb...@nondot.org
Reporter: lebedev...@gmail.com
CC: llvm-bugs@lists.llvm.org
void calle() {
#pragma omp cancel parallel
}
void caller() {
#pragma omp parallel
calle();
}
https://godbolt.org/z/_zYl80
^ gcc "error: orphaned '#pragma omp cancel' construct"
clang says it's ok
--
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 39844] Field ordering causes extra memcpy
https://bugs.llvm.org/show_bug.cgi?id=39844 Nikita Popov changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED Fixed By Commit(s)||https://reviews.llvm.org/rL ||349078 --- Comment #4 from Nikita Popov --- This has been fixed by https://reviews.llvm.org/rL349078. Godbolt for this code: https://cpp.godbolt.org/z/mphr26 -- 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 40192] New: Document trap representations of _Bool
https://bugs.llvm.org/show_bug.cgi?id=40192
Bug ID: 40192
Summary: Document trap representations of _Bool
Product: clang
Version: trunk
Hardware: All
OS: All
Status: NEW
Severity: enhancement
Priority: P
Component: Documentation
Assignee: unassignedclangb...@nondot.org
Reporter: gonzalob...@gmail.com
CC: llvm-bugs@lists.llvm.org, richard-l...@metafoo.co.uk
Compiling
unsigned int foo(unsigned int x, _Bool b) {
return x - (unsigned int)b;
}
only produces correct results if the value of `_Bool` is either `0` or `1`, see
https://gcc.godbolt.org/z/IqjQ-- :
foo: # @foo
mov eax, edi
sub eax, esi
ret
This probably means that all other representations of `_Bool` are trap
representations, but this does not appear to be documented anywhere.
>From my reading of the C standard, the role that padding bits play for `_Bool`
is unclear.
--
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 12042 in oss-fuzz: llvm/clang-format-fuzzer: Timeout in clang-format-fuzzer
Comment #2 on issue 12042 by ClusterFuzz-External: llvm/clang-format-fuzzer: Timeout in clang-format-fuzzer https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12042#c2 ClusterFuzz has detected this issue as fixed in range 201812300411:201812310412. Detailed report: https://oss-fuzz.com/testcase?key=5741869280002048 Project: llvm Fuzzer: libFuzzer_clang-format-fuzzer Fuzz target binary: clang-format-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Timeout (exceeds 25 secs) Crash Address: Crash State: clang-format-fuzzer Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201808010242:201808040250 Fixed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201812300411:201812310412 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5741869280002048 See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for instructions to reproduce this bug locally. If you suspect that the result above is incorrect, try re-doing that job on the test case report page. -- 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 12042 in oss-fuzz: llvm/clang-format-fuzzer: Timeout in clang-format-fuzzer
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #3 on issue 12042 by ClusterFuzz-External: llvm/clang-format-fuzzer: Timeout in clang-format-fuzzer https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12042#c3 ClusterFuzz testcase 5741869280002048 is verified as fixed, so closing issue as verified. If this is incorrect, please file a bug on https://github.com/google/oss-fuzz/issues/new -- 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 40167] unrelated template instantiation causes a section type conflict building using GCC 5.4
https://bugs.llvm.org/show_bug.cgi?id=40167 Andrew Paprocki changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #1 from Andrew Paprocki --- This is an AIX/XCOFF bug present in GCC 5.4 that was fixed in GCC 5.5 related to handling of COMDAT sections. -- 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 12352 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-loop_vectorize: Out-of-memory in llvm_llvm-opt-fuzzer--x86_64-loop_vectorize
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 Reproducible Engine-libfuzzer Proj-llvm Reported-2019-01-01 Type: Bug New issue 12352 by ClusterFuzz-External: llvm/llvm-opt-fuzzer--x86_64-loop_vectorize: Out-of-memory in llvm_llvm-opt-fuzzer--x86_64-loop_vectorize https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12352 Detailed report: https://oss-fuzz.com/testcase?key=5641751602135040 Project: llvm Fuzzer: libFuzzer_llvm_llvm-opt-fuzzer--x86_64-loop_vectorize Fuzz target binary: llvm-opt-fuzzer--x86_64-loop_vectorize Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Out-of-memory (exceeds 2048 MB) Crash Address: Crash State: llvm_llvm-opt-fuzzer--x86_64-loop_vectorize Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201802190622:201802200626 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5641751602135040 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 http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
