similar to: [LLVMdev] Please review fixes for llvm PR 15840

On Wed, Nov 26, 2014 at 07:44:20PM +0100, Dimitry Andric wrote: > On 26 Nov 2014, at 16:50, Tom Stellard <tom at stellard.net> wrote: > > > > On Wed, Nov 26, 2014 at 10:15:13AM +0000, Daniel Sanders wrote: > ... > > I will try to look at the patches today. I'm going to delay the release a week > > or so, because of all the merge requests I've received,

----- Original Message ----- > From: "Dimitry Andric" <dimitry at andric.com> > To: "Hal Finkel" <hfinkel at anl.gov> > Cc: "LLVM Developers Mailing List (llvmdev at cs.uiuc.edu)" <llvmdev at cs.uiuc.edu>, "Tom Stellard" <tom at stellard.net> > Sent: Saturday, November 29, 2014 1:34:21 PM > Subject: Re: [LLVMdev]

On Sat, Nov 29, 2014 at 08:34:34PM +0100, Dimitry Andric wrote: > On 29 Nov 2014, at 02:48, Tom Stellard <tom at stellard.net> wrote: > > On Wed, Nov 26, 2014 at 07:44:20PM +0100, Dimitry Andric wrote: > ... > >> I would like to propose the following additional patches for 3.5.1. These will already be part of the upcoming clang 3.5.0 import into the FreeBSD 11.0 base

On Wed, Dec 03, 2014 at 11:51:07AM -0800, Michael Zolotukhin wrote: > Hi Tom, > > I also have several patches that might be useful in 3.5.1. They all are stability fixes: > > r221009: Correctly update dom-tree after loop vectorizer. > r222451: Fix a trip-count overflow issue in LoopUnroll. > r223170 and r223171: PR21302.Vectorize only bottom-tested loops. > Hi Arnold,

On 22 Aug 2018, at 18:45, Hans Wennborg <hans at chromium.org> wrote: > > On Wed, Aug 22, 2018 at 3:48 AM, Dimitry Andric <dimitry at andric.com> wrote: >> On 22 Aug 2018, at 05:58, Wei Mi <wmi at google.com> wrote: >>> >>> On Fri, Aug 17, 2018 at 1:27 PM, Dimitry Andric <dimitry at andric.com> wrote: >>> On 16 Aug 2018, at 00:51,

On 22 Aug 2018, at 05:58, Wei Mi <wmi at google.com> wrote: > > On Fri, Aug 17, 2018 at 1:27 PM, Dimitry Andric <dimitry at andric.com> wrote: > On 16 Aug 2018, at 00:51, Joerg Sonnenberger via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > On Tue, Aug 07, 2018 at 09:49:16PM +0200, Dimitry Andric via llvm-dev wrote: > >> This is a regression caused by

On 9 Feb 2018, at 22:30, Dimitry Andric <dimitry at andric.com> wrote: > > On 9 Feb 2018, at 22:11, Dimitry Andric via Openmp-dev <openmp-dev at lists.llvm.org> wrote: >> >> On 9 Feb 2018, at 20:40, Dimitry Andric via cfe-dev <cfe-dev at lists.llvm.org> wrote: >>> >>>> On 9 Feb 2018, at 10:20, Hans Wennborg <hans at chromium.org>

On 19 Jul 2015, at 00:17, Dimitry Andric <dimitry at andric.com> wrote: > > On 17 Jul 2015, at 01:09, Hans Wennborg <hans at chromium.org> wrote: >> >> On Thu, Jul 16, 2015 at 3:47 PM, Dimitry Andric <dimitry at andric.com> wrote: >>> On 17 Jul 2015, at 00:31, Hans Wennborg <hans at chromium.org> wrote: >>>> >>>> Dear

On Mon, Jul 20, 2015 at 2:37 PM, Dimitry Andric <dimitry at andric.com> wrote: > On 20 Jul 2015, at 22:50, Hans Wennborg <hans at chromium.org> wrote: >> >> On Sat, Jul 18, 2015 at 3:17 PM, Dimitry Andric <dimitry at andric.com> wrote: >>> On 17 Jul 2015, at 01:09, Hans Wennborg <hans at chromium.org> wrote: >>>> >>>> On Thu,

On 19 Jan 2018, at 17:11, Hans Wennborg <hans at chromium.org> wrote: > > On Thu, Jan 18, 2018 at 7:27 PM, Dimitry Andric <dimitry at andric.com> wrote: >> On 18 Jan 2018, at 15:03, Jonas Hahnfeld <hahnjo at hahnjo.de> wrote: >>> >>> Am 2018-01-18 14:55, schrieb Dimitry Andric via llvm-dev: >>>> On 17 Jan 2018, at 18:53, Hans Wennborg

On Sun, Feb 11, 2018 at 3:31 PM, Dimitry Andric <dimitry at andric.com> wrote: > On 9 Feb 2018, at 22:30, Dimitry Andric <dimitry at andric.com> wrote: >> >> On 9 Feb 2018, at 22:11, Dimitry Andric via Openmp-dev <openmp-dev at lists.llvm.org> wrote: >>> >>> On 9 Feb 2018, at 20:40, Dimitry Andric via cfe-dev <cfe-dev at lists.llvm.org>

On Sun, Jul 19, 2015 at 8:32 AM, Dimitry Andric <dimitry at andric.com> wrote: > On 19 Jul 2015, at 01:44, Dimitry Andric <dimitry at andric.com> wrote: > ... >> Hm, strangely enough, this version of the script does not go further than the Phase 2 installation, and does not run any tests? This used to work fine for the release_36 branch. >> >> I think it is

On Sat, Jul 18, 2015 at 3:17 PM, Dimitry Andric <dimitry at andric.com> wrote: > On 17 Jul 2015, at 01:09, Hans Wennborg <hans at chromium.org> wrote: >> >> On Thu, Jul 16, 2015 at 3:47 PM, Dimitry Andric <dimitry at andric.com> wrote: >>> On 17 Jul 2015, at 00:31, Hans Wennborg <hans at chromium.org> wrote: >>>> >>>> Dear

It seems this is a cmake vs autoconf thing. With cmake, it builds correctly, but with autoconf I get the same error as you. I probably shouldn't have made this change while we were in the release process as it was potentially risky :-/ I've reverted it now, so hopefully the next build should be problem free. Thanks, Hans On Fri, Aug 21, 2015 at 5:09 AM, Dimitry Andric <dimitry at

On Thu, Jan 18, 2018 at 7:27 PM, Dimitry Andric <dimitry at andric.com> wrote: > On 18 Jan 2018, at 15:03, Jonas Hahnfeld <hahnjo at hahnjo.de> wrote: >> >> Am 2018-01-18 14:55, schrieb Dimitry Andric via llvm-dev: >>> On 17 Jan 2018, at 18:53, Hans Wennborg via Release-testers >>> <release-testers at lists.llvm.org> wrote: >>>> Start

Reported https://bugs.llvm.org/show_bug.cgi?id=38911 Thanks, Leslie Zhai 在 2018年09月11日 16:55, Dimitry Andric 写道: > Hi Leslie, > > The problem really lies in the OpenJDK code, as it is attempting to > write to a const object. If this seems to work with certain compiler(s) > and optimization settings, it is just luck. :-) > > Here is a reduced example, which shows the

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

On 31 Jan 2015, at 20:24, Hans Wennborg <hans at chromium.org> wrote: > > On Sat, Jan 31, 2015 at 9:24 AM, Dimitry Andric <dimitry at andric.com> wrote: ... >> This is because the ulimit -t 600 was exceeded, as shown in dmesg: >> >> pid 78288 (python2.7), uid 1000, was killed: exceeded maximum CPU limit >> >> Can we bump the -t limit a little?

On 19 Jul 2015, at 17:32, Dimitry Andric <dimitry at andric.com> wrote: > > On 19 Jul 2015, at 01:44, Dimitry Andric <dimitry at andric.com> wrote: > ... >> Hm, strangely enough, this version of the script does not go further than the Phase 2 installation, and does not run any tests? This used to work fine for the release_36 branch. >> >> I think it is

On Thu, Jul 16, 2015 at 3:47 PM, Dimitry Andric <dimitry at andric.com> wrote: > On 17 Jul 2015, at 00:31, Hans Wennborg <hans at chromium.org> wrote: >> >> Dear testers, >> >> 3.7.0-rc1 was just tagged; please start your testing engines :-) >> >> Upload binaries to the sftp and report your results to this thread. >> >> I'm sorry