similar to: [LLVMdev] Point Releases - tags

On 12 May 2014 10:29, "C. Bergström" <cbergstrom at pathscale.com> wrote: > I suspect 3.4.1 is based off > https://github.com/llvm-mirror/clang/tree/release_34 > > (llvm probably has something similar I suppose?) This is correct. Though, I don't know if anyone tagged 3.4.1 on that branch, but I suspect what was released is the HEAD of that branch. Tom would know

On 29 December 2015 at 08:08, Erik de Castro Lopo <mle+la at mega-nerd.com> wrote: > I would suggest: > > #if SIZEOF_VOIDP == 8 I believe this is not portable. At least on my machine ("4.2.1 Compatible FreeBSD Clang 3.4.1 (tags/RELEASE_34/dot1-final 208032)") it's not defined. Probably this one comes closest: #define __SIZEOF_POINTER__ 8 Riggs

On Thu, Jun 12, 2014 at 10:57:46AM +0200, Armin Steinhoff wrote: > > Hi, > > first problem was: > > >FileManager.cpp:311:21: error: range-based ‘for’ loops are not allowed > >in C++98 mode > >for (auto & fe: SeenFileEntries) { > >^ > >FileManager.cpp:312:14: error: request for member ‘getValue’ in ‘fe’, > >which is of non-class type ‘int’

On Mon, Jun 2, 2014 at 12:49 AM, Rui Ueyama <ruiu at google.com> wrote: > I agree to move these files to Core. Any objections? None here. - Michael Spencer > > On Mon, Jun 2, 2014 at 12:44 AM, Bas van den Berg > <b.van.den.berg.nl at gmail.com> wrote: >> >> The inverted dependency of Core to ReaderWriter via Simple.h was already >> present. >> My

Hi, I'm analysing the LLD code structure (aka architecture) and am trying to mold it into a component model. Currently I see 4 components: - Driver - ReaderWriter - Passes - Core I wonder if this is the order that they're supposed to be in, since there are also code dependencies upwards from: Core -> ReaderWriter Passes -> ReaderWriter ReaderWriter -> Driver For a

The inverted dependency of Core to ReaderWriter via Simple.h was already present. My idea was to fix the problem before it gets bigger. My proposal would be to move Simple.h and Alias.h to Core. Similar to UndefinedAtom.h etc. It would be even nicer to make the naming consistent as well, since there already is UndefinedAtom.h SharedLibaryAtom.h etc Maybe: SimpleAtom.h AliasAtom.h Moving the file

Yes, but if you look in LayoutPasses.c, it calls registry.referenceKindToString(..), so it does need the definition.. On Thu, Jul 10, 2014 at 2:30 PM, Jean-Daniel Dupas <mailing at xenonium.com> wrote: > Using forward-declaration would not fix the layer violation. > > Le 10 juil. 2014 à 13:10, Bas van den Berg <b.van.den.berg.nl at gmail.com> > a écrit : > > Well,

FreeBSD 9.3 Dovecot 2.25 (7be1766) I'm trying to install Dovecot2-pigeonhole-0.4.14_2 from ports. Get an error: cc1: error: unrecognized command line option "-Wno-duplicate-decl-specifier" With options MAKE_JOBS_UNSAFE=yes: cc1: error: unrecognized command line option "-Wno-duplicate-decl-specifier" *** [edit-mail.lo] Error code 1 Stop in

I added an listner to dovecot bye adding the following lines to config but no result no connectivity with ipv6: imap_listen = [::] pop3_listen = [::] imap_listen = * pop3_listen = * Met vriendelijk groet, Bas van Dikkenberg GISkit bv BFVD1-RIPE Tel: +3130-6340430 Fax: +3130-6342433 Prive Tel: +3130-6372769 Mob:

On 12 May 2014 14:33, Tom Stellard <tom at stellard.net> wrote: > Are you talking about adding git tags? What is the process for doing this? SVN tags, but yeah. You can take note of the commit that we produced the last candidate, but it'd be good to tag all repos with a release number. I'm not sure how people do it, but I'd assume the tags should follow the same as it's

On 19/05/2014 00:07, Anton Korobeynikov wrote: > The branch should already be there, because we mirror release_34 branch. > > We stopped to make tags ~ 2 releases ago, because git svn created > orphaned ones (mostly due to our directory layout - we do not "tag" a > particular commit, instead, we're creating separate dirs, etc.). Just to say, thanks for maintaining the

In stream_encoder.c there's the following code: #if defined FLAC__CPU_X86_64 /* and other 64-bit arch, too */ if(mean <= 0x80000000/512) { /* 512: more or less optimal for both 16- and 24-bit input */ #else if(mean <= 0x80000000/8) { /* 32-bit arch: use 32-bit math if possible */ #endif A) How to properly check for 64-bit architectures? I can check for "defined

Well, it does have a Registry& that's defined in Reader.h. But that can be forward declared (and apparently is in some of the other headers it includes. On Thu, Jul 10, 2014 at 12:08 PM, Andreas Wendleder < andreas.wendleder at googlemail.com> wrote: > Hi > > - passes depend on Reader and Writer >> > > That's an easy one. Compile tested on Windows with

Hi, I've been following the changes in LLD's software architecture. Recently a new file was added: Alias.h In this file, the curret Atom set is extended with an AliasAtom. While the change seems innocent enough, it has some nasty potential. Simple.h and Alias.h are placed in the ReaderWriter component. This is the 2nd component in the layering: Driver ReaderWriter Passes Core The problem

Hello! I was trying to optimize our automatically generated backend for Open RISC and for this purpose I went through the gcc torture testsuite. There are many programs that are better optimized by LLVM, but some are much better optimized by gcc 4.9. The main limitations were is loop unrolling and structures handling. Differences can be best seen e.g. when compiling for an

station month bas 190 5 0.000 190 7 1.563 190 10 0.000 190 11 0.000 202 4 18.750 202 5 18.750 202 7 6.250 202 10 4.800 202 11 3.125 198 4 18.750 198 5 31.250 198 7 3.125 198 10 3.200 198 11 12.500 205 4 0.000 205 5 0.000 205 7 0.000

Thanks for your reply Luis > Will be very helpful if you provide the logs (servicefb.log and > mongrel_service.log) both located into ruby\bin directory. --------------------------------------------------------------------------------- # Logfile created on 28/03/2007 17:54:32 native/process.bas:44, fb.process.spawn: Spawn() init native/process.bas:50, fb.process.spawn: Success in

I'm getting this error for al my users does anybody know wat the problem is and how i can fix it pop3(bas at giskit.nl): Mar 06 09:10:37 Error: file_wait_lock() failed with index file /mailstore/vmail/giskit.nl/bas/.INBOX/.imap.index: No locks available Met vriendelijk groet, Bas van Dikkenberg GISkit bv BFVD1-RIPE Tel: +3130-6340430 Fax:

Hi, I have just tagged the first release candidate for the 3.4.1 release, so testers may begin testing. Please refer to http://llvm.org/docs/ReleaseProcess.html for information on how to validate a release. If you have any questions or need something clarified, just email the list. For the 3.4.1 release we want to compare test results against 3.4-final. I have added support to the

Hi Tom, When running the test script, I got an error message: $ ./test-release.sh -no-64bit -release 3.4.2 -rc 1 -triple armv7a-linux-gnueabihf -j2 # Validating llvm SVN URL llvm 3.4.2 release candidate rc1 doesn't exist! Do I need to get another test-release.sh script? This is the one from release_34 branch we used to release 3.4.1. cheers, --renato On 16 May 2014 22:55, Tom Stellard