search for: __builtin_cfstring

...ing on it being in > a specific place, you have to mark it so LLVM knows it can't do > arbitrary manipulations on it. > I think that one of the problems with Objective-C (and why this became a problem in the first place) is that it does require the string to be in a specific place. The __builtin_CFString structure has, among other things, a field that points to the actual string. When this string isn't in the correct section, the linker complains. -bw

...be. If writable strings are disabled, writing to a string is undefined; it's not a bug if it doesn't crash. > I think that one of the problems with Objective-C (and why this became > a problem in the first place) is that it does require the string to be > in a specific place. The __builtin_CFString structure has, among other > things, a field that points to the actual string. When this string > isn't in the correct section, the linker complains. Mmm... if the __builtin_CFString structure has special properties to the linker, its strings really ought to be marked. There are all sor...

On Tue, Jan 27, 2009 at 1:00 PM, Bill Wendling <isanbard at gmail.com> wrote: > Even with C code, we place a null string in a writable > section, which isn't correct. You could say that, but it's not really wrong... say you had a 10 kilobyte struct that was all null. If you put it into a data section, it takes up 10k in the executable (unless Darwin has some unusual data

On Tue, Jan 27, 2009 at 9:06 AM, Anton Korobeynikov <anton at korobeynikov.info> wrote: > I'm strongly agains any target-specific and language-specific hacks in the > generic tree-conversion code. What if we decide to support objc on > non-darwin platforms someday? > This is theoretically possible (well, modulo all bunch of apple-local stuff > arond ;)). > > I