search for: blindspot

Hi all, the file samba-2.2.3a/source/script/installbin.sh has a rather odd blindspot. It doesn't honor the --with-privatedir= option to ./configure it just blindly uses $BASEDIR/private instead. I think the fix would be:- a) move directory creation out of installbin.sh altogehter (after all what's the installdirs: target for in the Makefile?) OR b) add an extra p...

...as done by the CRAN team for the package authors, in some cases even providing patches. Best Tomas > > On Wed, Apr 23, 2025 at 1:38?PM Tomas Kalibera <tomas.kalibera at gmail.com> wrote: >> On 4/23/25 19:03, Michael Chirico wrote: >>> h/t Tim Taylor for pointing out my blindspot :) >>> >>> We have Memcpy() in API already [1], which wraps a 0-aware R_chk_memcpy() [2]. >>> >>> We don't quite have Memset() in API, though; instead we have Memzero() >>> [3] for R_chk_memset(s, 0, n) which is 0-aware memset() [4]. >> I don...

...kyle+llvm at iteratee.net Cc: llvm-commits at lists.llvm.org iteratee created this revision. iteratee added a subscriber: llvm-commits. iteratee set the repository for this revision to rL LLVM. Currently the documented API for AnalyzeBranch leaves no place for conditional returns. This leaves a blindspot after shrinkwrapping on platforms with conditional return instructions. The existing API can be used to handle conditional returns by using a null TBB and a non-empty condition list. A null TBB should never mean fallthrough with a non-empty condition list, as that wouldn't make any sense. This...

>From R 4.5.0 [1], all builds of R discourage use of INTEGER() [and friends REAL(), ... and *_RO() equivalents] on length-0 SEXP [2]. Before R 4.5.0, this was the behavior under --enable-strict-barrier. That means the following can segfault under strict builds (e.g. -fsanitize=alignment and -O0): SEXP x = PROTECT(Rf_allocVector(INTSXP, 0)); SEXP y = PROTECT(Rf_allocVector(INTSXP, 0)); const

...perfectly fair to ask for more examples from the author and > digging a bit deeper if you're unconvinced that the proposed modeling can > be applicable outside of FIR. This is exactly why we ask such proposal to > go through RFC by the way: to allow people like you to point at the > blindspot and ask the right questions. > > Best, > > -- > Mehdi > > > >> > We would like to take advantage of the transformations in cases that >> are possible. FIR loops will be converted to affine/loop dialect. So the >> loop inside an omp.do can be in these dia...

...xamples from the author >>> and digging a bit deeper if you're unconvinced that the proposed modeling >>> can be applicable outside of FIR. This is exactly why we ask such proposal >>> to go through RFC by the way: to allow people like you to point at the >>> blindspot and ask the right questions. >>> >>> Best, >>> >>> -- >>> Mehdi >>> >>> >>> >>>> > We would like to take advantage of the transformations in cases that >>>> are possible. FIR loops will be converted t...

Reply to Kiran Chandramohan: > You are welcome to participate, provide feedback and criticism to change the design as well as to contribute to the implementation. Thank you Kiran. > But the latest is what is there in the RFC in discourse. I have used this as reference for the response. > We did a study of a few constructs and clauses which was shared as mails to flang-dev and the