search for: unprincipl

...th saying that symbol interposition falls outside of the > model we have for the targeted system (at least by default), and thus, this > is okay. We also don't model the possibility of someone hex-editing the > binary ;) > I'm not really okay with it; the current behavior feels unprincipled. We have a visibility attribute which can be used to control this: On ELF systems, "default" visibililty allows interposition (unlike on Darwin) -- that is, it explicitly ALLOWS for replacing the symbol's definition. The policy of "You can't replace the definition of the s...

On 5 January 2016 at 09:13, Renato Golin <renato.golin at linaro.org> wrote: > Anyhow, Artyom's proposal is the best, IMO, to treat it like an alias > and handle like v7A internally. If we end up needing specific > decisions in the driver, it should stay in the driver. That's rather a hack, given that the 'l' actually has semantic meaning, but I suppose I could live

----- Original Message ----- > From: "James Y Knight via llvm-dev" <llvm-dev at lists.llvm.org> > To: "Sanjoy Das" <sanjoy at playingwithpointers.com> > Cc: "llvm-dev" <llvm-dev at lists.llvm.org> > Sent: Thursday, February 25, 2016 1:41:43 PM > Subject: Re: [llvm-dev] Possible soundness issue with > available_externally (split

...l interposition falls outside > > of the model we have for the targeted system (at least by default), > > and thus, this is okay. We also don't model the possibility of > > someone hex-editing the binary ;) > > I'm not really okay with it; the current behavior feels unprincipled. > We have a visibility attribute which can be used to control this: On > ELF systems, "default" visibililty allows interposition (unlike on > Darwin) -- that is, it explicitly ALLOWS for replacing the symbol's > definition. The policy of "You can't replace the...

I noticed a change in LLVM's behavior between 3.2 and 3.3/ToT, but I'm not sure if it qualifies as a bug/regression or not. The change is that in 3.3 and tip of trunk, calling ConstantFoldConstantExpression on i64 and (i64 add (i64 add (i64 ptrtoint (i64* getelementptr (i64* null, i32 1) to i64), i64 ptrtoint (i64* getelementptr (i64* null, i32 1) to i64)), i64 15), i64 -16)

...l we have for the targeted system (at least by > > > default), > > > and thus, this is okay. We also don't model the possibility of > > > someone hex-editing the binary ;) > > > > > I'm not really okay with it; the current behavior feels > > unprincipled. > > > We have a visibility attribute which can be used to control this: > > On > > ELF systems, "default" visibililty allows interposition (unlike on > > Darwin) -- that is, it explicitly ALLOWS for replacing the symbol's > > definition. The policy...

...erposition falls outside of >> the model we have for the targeted system (at least by default), and thus, >> this is okay. We also don't model the possibility of someone hex-editing >> the binary ;) >> > > I'm not really okay with it; the current behavior feels unprincipled. > > We have a visibility attribute which can be used to control this: On ELF > systems, "default" visibililty allows interposition (unlike on Darwin) -- > that is, it explicitly ALLOWS for replacing the symbol's definition. The > policy of "You can't replace...

...A, so it should not have any > further knowledge about the rest of the environment. What does RTLinux on an R-class CPU present itself as? My guess would be "armv7l" too. I'm not too concerned about deciding that we only care about A-class Linux, but I am concerned about taking an unprincipled approach to the l/b suffix. Not enough that I can't live with it though. As you say this whole area's enough of a mess already, one more bit isn't going to break the world. Cheers. Tim.

...erposition falls outside of >> the model we have for the targeted system (at least by default), and thus, >> this is okay. We also don't model the possibility of someone hex-editing >> the binary ;) >> > > I'm not really okay with it; the current behavior feels unprincipled. > > We have a visibility attribute which can be used to control this: On ELF > systems, "default" visibililty allows interposition (unlike on Darwin) -- > that is, it explicitly ALLOWS for replacing the symbol's definition. The > policy of "You can't replace...

I still need to do some repetitive statistical analysis on some outcomes from a dataset. Take the following as an example; id sex hiv age famsize bmi resprate 1 M Pos 23 2 16 15 2 F Neg 24 5 18 14 3 F Pos 56 14 23 24 4 F Pos 67 3 33 31 5 M Neg 34 2 21 23 I want to know if there are statistically detectable differences in all of the continuous variables in

...possibility > > > > > > of > > > > > > someone hex-editing the binary ;) > > > > > > > > > > > > > > > > > > > > I'm not really okay with it; the current behavior feels > > > > > unprincipled. > > > > > > > > > > > > > > > We have a visibility attribute which can be used to control > > > > > this: > > > > > On > > > > > ELF systems, "default" visibililty allows interposition > &g...

The following is a message to be sent to the President of the United States of America. Although we may not be able to do a great deal from where we are, but for the people of America just knowing we care and feel their sadness will help. Please put your name on the following list and send it to all you know and who care. If you are the 100th name and every 100th there on could you please also