Displaying 9 results from an estimated 9 matches for "pr35804".
2018 Jan 03
2
[6.0.0 Release] The release branch is here; trunk is now 7.0.0
...that this time we're doing an early "slow start" of the release
process. I'm still on vacation and there is no release candidate
scheduled until 17 January, but those interested can start testing and
nominating patches for merging.
Release blockers are tracked by https://llvm.org/PR35804 Please mark
any bugs, old or new, that need to be fixed as blocking that.
To get a change committed to the branch, first commit it to trunk as
usual, and then request it to be merged --- ideally by filing a
blocker bug on PR35804, or by cc'ing me on the commit email.
Please help out with the...
2018 Jan 08
0
[cfe-dev] [6.0.0 Release] The release branch is here; trunk is now 7.0.0
Hi Hans,
> To get a change committed to the branch, first commit it to trunk as
> usual, and then request it to be merged --- ideally by filing a
> blocker bug on PR35804, or by cc'ing me on the commit email.
>
What about adding a project to the list of projects ported to LLVM 6.0
in `docs/ReleaseNotes.rst`? I have a project that I've just ported to
LLVM 6.0 that I'd like to add to that list.
It doesn't make a huge amount of sense to commit that...
2018 Jan 10
2
[cfe-dev] [6.0.0 Release] The release branch is here; trunk is now 7.0.0
...o it for you.
Thanks,
Hans
On Mon, Jan 8, 2018 at 8:31 AM, Dan Liew <dan at su-root.co.uk> wrote:
> Hi Hans,
>
>> To get a change committed to the branch, first commit it to trunk as
>> usual, and then request it to be merged --- ideally by filing a
>> blocker bug on PR35804, or by cc'ing me on the commit email.
>>
>
> What about adding a project to the list of projects ported to LLVM 6.0
> in `docs/ReleaseNotes.rst`? I have a project that I've just ported to
> LLVM 6.0 that I'd like to add to that list.
>
> It doesn't make a hug...
2018 Feb 09
0
[6.0.0 Release] Release Candidate 2 source, docs and binaries available
Hello everyone,
Source, docs and binaries for LLVM-6.0.0-rc2 are now available at
http://prereleases.llvm.org/6.0.0/#rc2
I'll add more binaries as they become available.
Please report any problems you find, ideally as bugs marked as
blockers of http://llvm.org/PR35804
Thanks,
Hans
2018 Feb 19
2
[6.0.0 Release] TIme to wrap it up
...e.
We won't make it to the final tag on the 21st as per the schedule, but
I would like to get all outstanding blockers fixed and rc3 tagged by
Friday. Hopefully this would be the last rc and we could go to final
soon after.
If you're involved in a release-blocking bug (see
http://llvm.org/PR35804), please try to get it resolved as soon as
possible.
If you were planning to run some additional testing before the
release, it's high time.
I would also like to get the release notes ready this week. If you've
been meaning to write something but didn't get around to it yet, now
is th...
2018 Feb 26
0
[6.0.0 Release] Release Candidate 3 source, docs and binaries available
Hi everyone,
The source, docs and binaries for LLVM-6.0.0-rc3 are now available at
http://prereleases.llvm.org/6.0.0/#rc3
More binaries will be added as they become available.
Please report any problems you find as bugs marked blocking
http://llvm.org/PR35804
If this looks good, the final tag will go in real soon now.
Thanks,
Hans
2018 Feb 19
0
LLVM Weekly - #216, Feb 19th 2018
...utes could be
inferred.
* Hans Wennborg
[indicates](http://lists.llvm.org/pipermail/llvm-dev/2018-February/121295.html)
that the 6.0.0 final tag won't be made by the 21st of Feb (as in the original
release schedule), but the hope is to have rc3 tagged by Friday with [release
blockers](llvm.org/PR35804) fixed.
## LLVM commits
* The width of the GEP (getelemenptr) index used in address calculation can
now be specified using the data layout string.
[r325102](http://reviews.llvm.org/rL325102).
* LLVM will now try harder to report a fatal error when out of memory (when
memory allocation fails). [...
2018 Feb 12
1
[Openmp-dev] [cfe-dev] [Release-testers] [6.0.0 Release] Release Candidate 2 tagged
I noticed a problem with llvm-config.exe on Windows:
>"c:\Users\andy\llvm+clang-6.0.0rc2-win64-msvc-release\bin\llvm-config.exe" --system-libs
psapi.lib shell32.lib ole32.lib uuid.lib
But then when I link against LLVM and these libs, I get:
lld: error: LLVMSupport.lib(Process.obj): undefined symbol:
__imp_CryptAcquireContextW
lld: error: LLVMSupport.lib(RandomNumberGenerator.obj):
2018 Feb 09
3
retpoline mitigation and 6.0
I think I see what's going on, and I agree it looks like a bug. It was too
much to hope that later passes weren't going to mess with the PUSH
instruction. :(
While I was trying to reproduce your problem, I think I found another one
that looks like this:
$ clang -S -O2 -m32 -mregparm=3 -mretpoline spill_across_rp.cpp -o - |
grep _retpoline_push -B2
...
movl %eax, 8(%esp)