similar to: [LLVMdev] (Not) instrumenting global string literals that end up in .cstrings on Mac

Displaying 20 results from an estimated 2000 matches similar to: "[LLVMdev] (Not) instrumenting global string literals that end up in .cstrings on Mac"

2013 Mar 21
0
[LLVMdev] (Not) instrumenting global string literals that end up in .cstrings on Mac
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
2009 Jan 27
4
[LLVMdev] RFC: -fwritable-strings Change
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
2009 Jan 27
0
[LLVMdev] RFC: -fwritable-strings Change
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
2009 Jan 10
2
[LLVMdev] How to represent zero-sized string?
Hi all, int main() { t(""); return 0; } On Mac OS X, llvm-gcc compiles the zero-sized string to: .lcomm LC,1,0 gcc: .cstring LC0: .ascii "\0" The difference seems innocent enough. However, in objc if the zero- sized string is part of a cfstring, it causes a problem. The linker expects it in the readonly __cstring section, but llvm puts it in the
2009 Jan 10
0
[LLVMdev] How to represent zero-sized string?
On Fri, Jan 9, 2009 at 5:40 PM, Evan Cheng <evan.cheng at apple.com> wrote: > The difference seems innocent enough. However, in objc if the zero- > sized string is part of a cfstring, it causes a problem. The linker > expects it in the readonly __cstring section, but llvm puts it in the > read / write bss section. That seems extremely weird... what sort of magic is objc using
2018 Sep 05
2
AddressSanitizer on SPECCPU2006
Hi Alex Thanks for your email. But it seems not work. I removed the -fsanitize=address flag. The global buffer overflow message doesn't show. However, no *.sancov file is created after I run perlbench. Thus, I could not get the BB coverage. Do you have any ideas? Many Thanks Regards Muhui Alexander Potapenko <glider at google.com> 于2018年9月5日周三 下午7:14写道: > Hi Muhui, > > If
2018 Sep 05
2
AddressSanitizer on SPECCPU2006
Hi If so, is it able to disable this check. All I need is just to get the BB coverage information Regards Muhui Alexander Potapenko <glider at google.com>于2018年9月5日 周三下午6:57写道: > This is a known problem in SPECCPU2006, see > https://github.com/google/sanitizers/wiki/AddressSanitizerFoundBugs > On Wed, Sep 5, 2018 at 7:36 AM Muhui Jiang via llvm-dev > <llvm-dev at
2011 Nov 29
2
[LLVMdev] Instrumentation passes and -O0 optimization level
> >> + EP_EnabledOnOptLevel0 > > I'd rename this as EP_AlwaysEnabled > Renamed, see the attachment. But note that one needs to add his pass at two extension points: at O0 and wherever else he wanted to add it. Won't such a name confuse the user? E.g. he may think that just adding a pass as "EP_AlwaysEnabled" should be enough to have it at any optimization
2013 Nov 20
2
[LLVMdev] Can't compile compiler-rt, asan error
I'm running Mavericks. I'll attach the make log once it's done. ________________________________ > Date: Wed, 20 Nov 2013 08:40:12 +0400 > Subject: RE: [LLVMdev] Can't compile compiler-rt, asan error > From: glider at google.com > To: yuchenericwu at hotmail.com > CC: llvmdev at cs.uiuc.edu > > > Also, which version of OSX you're running? >
2013 Nov 20
2
[LLVMdev] Can't compile compiler-rt, asan error
Can you please reconfigure and attach the full log of 'make VERBOSE=1' ? On Nov 20, 2013 8:25 AM, "Yuchen Wu" <yuchenericwu at hotmail.com> wrote: > It looks like it: > > [/Volumes/Files/yuchen_wu/dev/llvm/build]$ xcrun --show-sdk-path --sdk > iphonesimulator > >
2013 Nov 19
1
[LLVMdev] Broken build: r194813
Hi, can you please check the problem is fixed by r195125? On Tue, Nov 19, 2013 at 2:35 PM, Alexander Potapenko <glider at google.com> wrote: > Hi Cameron, > > I'm planning to address this issue today. > > HTH, > Alex > > On Mon, Nov 18, 2013 at 9:45 PM, Cameron McInally > <cameron.mcinally at nyu.edu> wrote: >> Hey guys, >> >> My local
2015 Jun 26
2
Driver macosx-ups failing on Yosemite
OSX Yosemite 10.10.3 Nut version 2.6.5 Installed via Macports Device is Cyberpower CP1000AVRLCD Device is visible and is monitored in the OSX control panel Error- macosx-ups -DD -a cyberpower Network UPS Tools - Mac OS X UPS meta-driver 1.0 (2.6.5-Unversioned directory) Warning: This is an experimental driver. Some features may not function correctly. 0.000000 debug level is '2'
2015 Jun 27
4
Driver macosx-ups failing on Yosemite
On Jun 27, 2015, at 9:17 AM, Charles Lepple <clepple at gmail.com> wrote: > On Jun 26, 2015, at 11:07 PM, Sundeep Mediratta <smedius at gmail.com> wrote: > >> 0.000233 upsdrv_initups(): Power Sources blob: >> <CFArray 0x7ffd18605480 [0x7fff7443bed0]>{type = immutable, count = 1, values = ( >> 0 : <CFBasicHash 0x7ffd18605360 [0x7fff7443bed0]>{type
2013 Nov 18
2
[LLVMdev] Broken build: r194813
Hey guys, My local build is broken after: >r194813 | glider | 2013-11-15 08:13:01 -0500 (Fri, 15 Nov 2013) | 2 lines > >[ASan] Add the configure+make rules for building the ASan runtime for iOS > simulator. Tim Northover was kind enough to track this down to a dependency on the “iphonesimulator” SDK. How should this issue be resolved? I'm currently following the receipe to build
2019 Aug 01
2
Dead store elimination in the backend for -ftrivial-auto-var-init
On Thu, Aug 1, 2019 at 6:38 PM JF Bastien <jfbastien at apple.com> wrote: > > > > > On Aug 1, 2019, at 9:20 AM, Alexander Potapenko <glider at google.com> wrote: > > > > On Thu, Aug 1, 2019 at 6:09 PM JF Bastien <jfbastien at apple.com> wrote: > >> > >> Hi Alexander, > >> > >> The code doesn’t compile. Could you send
2013 Nov 20
0
[LLVMdev] Can't compile compiler-rt, asan error
Also, which version of OSX you're running? On Nov 20, 2013 8:32 AM, "Alexander Potapenko" <glider at google.com> wrote: > Can you please reconfigure and attach the full log of 'make VERBOSE=1' ? > On Nov 20, 2013 8:25 AM, "Yuchen Wu" <yuchenericwu at hotmail.com> wrote: > >> It looks like it: >> >>
2013 Nov 20
2
[LLVMdev] Can't compile compiler-rt, asan error
"If the answer is no", of course. On Nov 20, 2013 8:02 AM, "Alexander Potapenko" <glider at google.com> wrote: > Do you have the iossim sdk installed on your machine (check by 'xcrun > --show-sdk-path --sdk iphonesimulator')? > If the answer is yes and you're testing on ToT, that's a bug. I'll take a > look. > On Nov 20, 2013 5:05 AM,
2019 Aug 07
2
Dead store elimination in the backend for -ftrivial-auto-var-init
There are two problems: 1. padding after union and call to q(), without LTO we can't remove that store. 2. shortcut which I have which ignores all instructions q() . this assume that memset to acpar.match, acpar.matchinfo also useful which is not true. I should be able to improve this case. On Thu, Aug 1, 2019 at 11:29 PM Vitaly Buka <vitalybuka at google.com> wrote: > On a first
2011 Nov 30
0
[LLVMdev] Instrumentation passes and -O0 optimization level
On Tue, Nov 29, 2011 at 8:56 AM, Alexander Potapenko <glider at google.com>wrote: > PS. Should we move the discussion to cfe-commits or it's ok to > continue the review process here? > For future reference, please send patches which touch both LLVM and Clang to llvm-commits and cfe-commits. However, looking at the Clang side of the patch, it is totally fine. =D --------------
2013 Nov 20
0
[LLVMdev] Can't compile compiler-rt, asan error
I tracked down the error. There’s an ifneq check for IOSSIM_SDK_PATH before it’s defined. $ grep -n IOSSIM_SDK_PATH projects/compiler-rt/make/platform/clang_darwin.mk 91:ifneq ($(IOSSIM_SDK_PATH),) 157:IOSSIM_SDK_PATH := $(call XCRunSdkPath,iphonesimulator) 158:$(warning clang_darwin.mk: $(IOSSIM_SDK_PATH)) 161: -isysroot $(IOSSIM_SDK_PATH) \ 207: -mios-simulator-version-min=7.0