similar to: Help upgrading to 1.1.3 (MD5 sum issues, album art corrupts files)

--- "Stephen F. Booth" <me@sbooth.org> wrote: > Hello all, > > I recently upgraded the libFLAC used in my application Max (http:// > sbooth.org/Max/) to 1.1.3 and added preliminary support for album > art. During the upgrade I evidently made some coding mistakes with > interesting results. I've combed everything over and can't quite see > the

List, I''m trying to build wxRuby on MacOS X 10.4.6 (intel). I''ve come across some of the problems mentioned on the list, i.e. the RubyConstant issue and the "id" keyword conflict issue. however somethings''s happening that as far as I can see has not been mentioned on the list. here''s the first few lines of the build fail report:

(forgot to CC llvmdev) On Thu, Mar 21, 2013 at 5:54 PM, Alexander Potapenko <glider at google.com> wrote: > Hey Anna, Nick, Ted, > > We've the following problem with string literals under ASan on Mac. > Some global string constants end up being put into the .cstring > section, for which the following rules apply: > - the strings can't contain zeroes in their

Alexander, On Darwin the "__cstring" section (really section with type S_CSTRING_LITERAL) is defined to contain zero terminate strings of bytes that the linker can merge and re-order. If you want pad bytes before and after the string, you need to put the strings in a different section (e.g. __TEXT, __const). But, CF/NSString literals will be problematic. The compiler emits a static

Dear community, I'm using gnustep runtime -fobjc-runtime=gnustep with gnustep-libobjc2 (https://github.com/gnustep/libobjc2) and Cocotron/Chameleon. For following source file #import <Foundation/Foundation.h> #import <UIKit/UIKit.h> int main(void) {         NSString *str = [NSString stringWithCString:"TEST"];

On 5/8/2013 2:45 PM, Nick Kledzik wrote: > > I'd rather we use a crypto hash so we don't have to compare content at all. > The crypto hashes work well if the atom content is const data (e.g. c-string or other literals), since you just point the hash function at the range of bytes in the constant data. Where it gets messier is if you are trying to coalesce non-leaf functions or

Hi Reid, Thanks for the reply. Comments inline below. Regards, Eric On 9/29/14, 5:51 PM, Reid Kleckner wrote: > I think any port will involve some changes, but it's really hard to > say which porting approach will be the least painless beforehand. > Aside from _MSC_VER incompatibilities messing up portability headers, > I think any changes you make to support clang on Windows

Dear R users, I am running R 2.10.0 on OS X 10.5.8. I had been running 2.10 successfully for about a week (and have used previous R versions for 2+ years on the same computer) until 2 days ago it failed to start up for me. Now when I try to start R, the application tries to initiate for several minutes then crashes. Looking at the activity monitor, my memory usage goes from having about 1.6Gb

Dear R users, I am running R 2.10.0 on OS X 10.5.8. I had been running 2.10 successfully for about a week (and have used previous R versions for 2+ years on the same computer) until 2 days ago it failed to start up for me. Now when I try to start R, the application tries to initiate for several minutes then crashes. Looking at the activity monitor, my memory usage goes from having about 1.6Gb

Dear R-gurus, I'm trying to compile R on my new mac. It's snow leopard. So far I've seemed to be doing pretty well. I've looked at http://cran.r-project.org/bin/macosx/tools/ http://r.research.att.com/exp/ http://r.research.att.com/building.html http://r.research.att.com/tools/ All of which have been very helpful. Looking at the threads I've got around some X11 issues

I've been having somewhat semi-random crashes that seem to be related to my use of Argument objects, usually when I then try to use them for processing, for examples in a CallInst. Do I need to copy or wrap the Argument if I want to use it as a Value? Or can I just use the reference that I am getting (multiple times)? I think there is probably something very fundamental about the

Hi guys, I've been using blocks for a while and found that current behavior is error prone. So I am going to propose to you the better one. Motivation: 1) The __weak variables in blocks are very common pattern. So having any implicit default behavior makes thing worse. 2) Some stupid mistakes like: __weak typeof (self) theSelf = self; ...^ { theSelf.blabla = .. .... [self blabla];

Sorry if this isn't the right place; but I'm facing an XCode 4 (LLVM 2.0 to Apple, I heard it's LLVM 2.9 under the hood) issue that may involve LLVM, and maybe some people on this list could help me short-circuit the source. I have a code pattern that, when used in XCode 4 in Objective C++ files, causes the whole IDE to go crash. It is a stripped sample to highlight the issue. In

On Mon, 22 Jan 2007, Marcel Weiher wrote: > I've been having somewhat semi-random crashes that seem to be related > to my use of Argument objects, usually when I then try to use them for > processing, for examples in a CallInst. Your code looks pretty reasonable to me. The only thing to be aware of is that varargs functions will have fewer Argument nodes than calls to the

Hi folks, just installed the new llvm 1.9 build and noticed that my code no longer worked. It seems something has changed with addPassesToEmitFile(). First, the arguments to that method changed so that it no longer takes a PassManager, but only a FunctionPassManager. Instead there is a addPassesToEmitWholeFile() method, but that is marked as optional, and when I change my code to

Hello Michael, > The module dump suggests everything is right, i can see in the function call the struct with the values 10 and 25, but the function is only received the 10 for the x field, nothing for the y field.  Am I missing something? You're missing the Platform ABI. I assume you're on x86-64, then your struct (according to the ABI) should be passed in a single 64 bit register as

On Jan 26, 2009, at 4:07 PMPST, Bill Wendling wrote: > There is a problem with Objective-C code where a null string is placed > in the wrong section. If we have this code: > > #include <Foundation/Foundation.h> > void foo() { > NSLog(@""); > } > > The null string is defined like this: > > .const > .lcomm LC,1,0 ## LC > > Causing our

There is a problem with Objective-C code where a null string is placed in the wrong section. If we have this code: #include <Foundation/Foundation.h> void foo() { NSLog(@""); } The null string is defined like this: .const .lcomm LC,1,0 ## LC Causing our linker to go nuts, because it expects anonymous strings to be in the __cstring section. I came up with the attached

Dear community, I faced with code which was generated by llvm, assembly instructions of that code is relying on 8-bytes alignment for structures on the stack. The part of Objective C code is following: -(void)getCharacters:(unichar *)unicode {     NSRange range;     range.location = 0;     range.length = [self length];     printf("%p, %p\n", &range.location, &range.length); And

I've been working on a wrapper for LLVM's C++ API to use from Objective-C for a scripting language I'm working on. I currently have an issue with passing arguments to a function that takes a struct argument. typedef struct _test_struct { int x; int y; } test_struct; id testLLVMStructFuncCall(test_struct x) { NSLog(@"%d %d",x.x,x.y); return N(x.x + x.y); }