search for: release_381

Hi Tom, Hi Anton, the first I had in mind was... "Another (LLVM/CLang) realease - a new drama!" ( See Byron Katie "The work". ) I know SVN is your 1st development platform. Personally, I prefer Git and use the LLVM/Clang mirrors on GitHub. Unfortunately, I am missing a "release_381" branch at all on the GitHub repositories. I looked through the llvm-commits [1] and I only see two emails with the subject... "Creating release candidate final from release_381 branch" [test-suite] r273407 - Creating release candidate final from release_381 branch Tom Stellard...

...inal has been tested successfully. :) >>> They'll be announced in the list and available here: >>> http://llvm.org/releases/download.html#3.8.1 >> Thanks you both for your answers. >> Can you or Tom (as release-manager) answer why there were no >> commit-ids (release_381 SVN branch) sent to llvm-commits ML? > Sure, I already written this above - there is *no* such branch > (http://llvm.org/svn/llvm-project/llvm/branches/) > Hmm, I saw this on llvm-commits ML... [test-suite] r273407 - Creating release candidate final from release_381 branch http://lists.l...

...essfully. > >>> :) They'll be announced in the list and available here: > >>> http://llvm.org/releases/download.html#3.8.1 > >> Thanks you both for your answers. > >> Can you or Tom (as release-manager) answer why there were no > >> commit-ids (release_381 SVN branch) sent to llvm-commits ML? > > Sure, I already written this above - there is *no* such branch > > (http://llvm.org/svn/llvm-project/llvm/branches/) > > > > Hmm, I saw this on llvm-commits ML... > > [test-suite] r273407 - Creating release candidate final from...

...t coming, now that final has been tested successfully. :) >> They'll be announced in the list and available here: >> http://llvm.org/releases/download.html#3.8.1 > Thanks you both for your answers. > Can you or Tom (as release-manager) answer why there were no > commit-ids (release_381 SVN branch) sent to llvm-commits ML? Sure, I already written this above - there is *no* such branch (http://llvm.org/svn/llvm-project/llvm/branches/) -- With best regards, Anton Korobeynikov Department of Statistical Modelling, Saint Petersburg State University

...ad in mind was... > "Another (LLVM/CLang) realease - a new drama!" > ( See Byron Katie "The work". ) > > I know SVN is your 1st development platform. > Personally, I prefer Git and use the LLVM/Clang mirrors on GitHub. > > Unfortunately, I am missing a "release_381" branch at all on the > GitHub repositories. > > I looked through the llvm-commits [1] and I only see two emails with > the subject... > > "Creating release candidate final from release_381 branch" > > [test-suite] r273407 - Creating release candidate final fr...

...hey'll be announced in the list and available here: >>> >>> http://llvm.org/releases/download.html#3.8.1 >>> >> Thanks you both for your answers. >>> >> Can you or Tom (as release-manager) answer why there were no >>> >> commit-ids (release_381 SVN branch) sent to llvm-commits ML? >>> > Sure, I already written this above - there is *no* such branch >>> > (http://llvm.org/svn/llvm-project/llvm/branches/) >>> > >>> >>> Hmm, I saw this on llvm-commits ML... >>> >>> [test...

...ans-fp-math"="false" "stack-protector-buffer-size"="8" "target-features"="+mmx,+sse,+sse2" "unsafe-fp-math"="false" "use-soft-float"="false" } !llvm.ident = !{!0} !0 = !{!"clang version 3.8.1 (tags/RELEASE_381/final)"} Thanks, Michael -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20170407/754f93c4/attachment.html>

..." "target-features"="+mmx,+sse,+sse2" >>>> "unsafe-fp-math"="false" "use-soft-float"="false" } >>>> >>>> !llvm.ident = !{!0} >>>> >>>> !0 = !{!"clang version 3.8.1 (tags/RELEASE_381/final)"} >>>> >>>> Thanks, >>>> Michael >>>> >>>> _______________________________________________ >>>> LLVM Developers mailing list >>>> llvm-dev at lists.llvm.org >>>> http://lists.llvm.org/cgi-bin...

...gt;>> :) They'll be announced in the list and available here: >> >>> http://llvm.org/releases/download.html#3.8.1 >> >> Thanks you both for your answers. >> >> Can you or Tom (as release-manager) answer why there were no >> >> commit-ids (release_381 SVN branch) sent to llvm-commits ML? >> > Sure, I already written this above - there is *no* such branch >> > (http://llvm.org/svn/llvm-project/llvm/branches/) >> > >> >> Hmm, I saw this on llvm-commits ML... >> >> [test-suite] r273407 - Creating r...

...re just coming, now that final has been tested successfully. :) > > They'll be announced in the list and available here: > > http://llvm.org/releases/download.html#3.8.1 > Thanks you both for your answers. Can you or Tom (as release-manager) answer why there were no commit-ids (release_381 SVN branch) sent to llvm-commits ML? Can you answer my question on how to set the version-string correct when generating tarballs out of the release_38 Git branch? ( I generated source-tarballs out of my local Git repositories, see below. ) - Sedat - [ INSTRUCTIONS: GENERATE TARBALLS OUT OF GIT...

On 26 June 2016 at 13:31, Anton Korobeynikov via llvm-dev <llvm-dev at lists.llvm.org> wrote: > What you're probably missing is that 3.8.1 is made in release_38 > branch. So, everything is there and already mirrored. > > Source tarballs will be available upon the release. Which are just coming, now that final has been tested successfully. :) They'll be announced in the

...tack-protector-buffer-size"="8" "target-features"="+mmx,+sse,+sse2" >> "unsafe-fp-math"="false" "use-soft-float"="false" } >> >> !llvm.ident = !{!0} >> >> !0 = !{!"clang version 3.8.1 (tags/RELEASE_381/final)"} >> >> Thanks, >> Michael >> >> _______________________________________________ >> LLVM Developers mailing list >> llvm-dev at lists.llvm.org >> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev >> >> > --------------...

> I’ve seen the same problem, but didn’t find solution back then. > I can give a hint that it is related to a thread local storage (notice TLS in the name). > > The same result can be reproduced by this simple program: > > thread_local int x = 0; > int main() { > return 0; > } > >When compiled into IR it produces similar error: > >LLVM ERROR:

...i16 %4, -1017 %6 = or i16 %5, 984 store i16 %6, i16* getelementptr inbounds (%struct.anon, %struct.anon* @Packet, i32 0, i32 3), align 1 store i8 1, i8* getelementptr inbounds (%struct.anon, %struct.anon* @Packet, i32 0, i32 4), align 1 ret void } !0 = !{!"clang version 3.8.1-24 (tags/RELEASE_381/final)"} ------------------------------ With best regards, Dmitry Ponyatov, Icbcom, IoT/embedded engineer, tel. +7 917 10 10 818 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180601/38be8953/attachme...

...;Prologue/Epilogue Insertion & Frame Finalization' on function '@_ZN4llvm21PrettyStackTraceEntryD0Ev' clang-3.8: error: unable to execute command: Aborted (core dumped) clang-3.8: error: clang frontend command failed due to signal (use -v to see invocation) clang version 3.8.1 (tags/RELEASE_381/rc1) Target: i686-pc-linux-gnu Thread model: posix InstalledDir: /usr/bin clang-3.8: note: diagnostic msg: PLEASE submit a bug report to http://llvm.org/bugs/ and include the crash backtrace, preprocessed source, and associated run script. clang-3.8: note: diagnostic msg: ******************** PLEAS...

...t; > "target-cpu"="x86-64" "target-features"="+fxsr,+mmx,+sse,+sse2" > "unsafe-fp-math"="false" "use-soft-float"="false" } > > !llvm.ident = !{!0} > > !0 = !{!"clang version 3.8.1-12 (tags/RELEASE_381/final)"} > > > 2017-02-07 16:19 GMT+00:00 Gaetano Checinski <gaetano.checinski at gmail.com> > : > >> > I’ve seen the same problem, but didn’t find solution back then. >> > I can give a hint that it is related to a thread local storage (notice >> TL...

Dear testers, 3.9.0-rc1 was just tagged from the 3.9 branch at r277207. This took a little longer than I'd hoped, but I think the branch is in a decent state now. There are still open merge requests and bugs, but I'd like to get the real testing started to see where we're at. Please build, test, and upload binaries to the sftp. Let me know how it goes. I'll upload source, docs,

On Wed, Jul 13, 2016 at 04:48:51PM +0200, Sedat Dilek via llvm-dev wrote: > [ CCed all people who were involved in this thread ] > > Hi Tom, > > personally, I am interested to test the prebuilt-toolchains for > Ubuntu/xenial alias 16.04 LTS and Debian/Jessie v8.5.0 AMD64. > The available toolchains are incomplete and thus useless. > > Just as a fact: There is still no