search for: libirs

Hi, I have gnuwin32 (b18) and the rw0613b.zip version of R. With regards to (re)making the dynload dll demo given (zero.dll) could anyone tell me what the command line for the makefile should be. ie, make -f Makefile.in ...? Thanks for any help -- Douglas -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- r-help mailing list -- Read

On 02/12/2019 10:07, Stefan G. Weichinger via samba wrote: > Am 02.12.19 um 08:47 schrieb L.P.H. van Belle via samba: >> Hai, >> >> Sorry for the late reply. > Never mind, weekend is important ... > >> Here its just apt-get distupgrade --autoremove --purge >> Without the autoremove libldb1 is not removed so libldb2 can be installed. > # apt-get distupgrade

-- 此致 礼 罗勇刚 Yours sincerely, Yonggang Luo -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20161115/80fd3c17/attachment.html>

...g Paketaktualisierung (Upgrade) wird berechnet... Fertig Die folgenden Pakete werden ENTFERNT: g++-6* guile-2.0-libs* libavahi-client3* libavahi-common-data* libavahi-common3* libbind9-140* libcups2* libcurl3* libdbus-glib-1-2* libdns162* libenca0* libexempi3* libexif12* libicu57* libiptcdata0* libirs-export141* libisc160* libisccc-export140* libisccc140* libisccfg-export140* libisccfg140* libjansson4* libkdb5-8* liblwres141* libmariadbclient18* libnss-winbind* libpam-winbind* libperl5.24* libpython3.5* libpython3.5-dev* libpython3.5-minimal* libpython3.5-stdlib* libsmbclient* libstdc++-6-dev*...

...grade) wird berechnet... Fertig > Die folgenden Pakete werden ENTFERNT: > g++-6* guile-2.0-libs* libavahi-client3* libavahi-common-data* > libavahi-common3* libbind9-140* libcups2* libcurl3* libdbus-glib-1-2* > libdns162* libenca0* libexempi3* libexif12* libicu57* libiptcdata0* > libirs-export141* libisc160* libisccc-export140* libisccc140* > libisccfg-export140* libisccfg140* libjansson4* libkdb5-8* > liblwres141* > libmariadbclient18* libnss-winbind* libpam-winbind* libperl5.24* > libpython3.5* libpython3.5-dev* libpython3.5-minimal* > libpython3.5-stdlib* libs...

...ade) wird berechnet... Fertig > Die folgenden Pakete werden ENTFERNT: > g++-6* guile-2.0-libs* libavahi-client3* libavahi-common-data* > libavahi-common3* libbind9-140* libcups2* libcurl3* libdbus-glib-1-2* > libdns162* libenca0* libexempi3* libexif12* libicu57* libiptcdata0* > libirs-export141* libisc160* libisccc-export140* libisccc140* > libisccfg-export140* libisccfg140* libjansson4* libkdb5-8* liblwres141* > libmariadbclient18* libnss-winbind* libpam-winbind* libperl5.24* > libpython3.5* libpython3.5-dev* libpython3.5-minimal* > libpython3.5-stdlib* libsmbcli...

On Feb 17, 2015, at 1:58 PM, Chandler Carruth <chandlerc at gmail.com> wrote: > I'm not actually worried about this change though Chris, at least w.r.t. optimizer changes being necessary. There are a few reasons: > > 1) The old ScalarRepl pass cared a *lot* about pointer type, but the new SROA doesn't care at all, so the biggest offender is essentially handled. Why do you

On Tue, Feb 17, 2015 at 10:47 PM, David Blaikie <dblaikie at gmail.com> wrote: > > > On Tue, Feb 17, 2015 at 10:27 PM, Chris Lattner <clattner at apple.com> > wrote: > >> On Feb 17, 2015, at 1:58 PM, Chandler Carruth <chandlerc at gmail.com> >> wrote: >> > I'm not actually worried about this change though Chris, at least >> w.r.t.

On Wed, Feb 18, 2015 at 6:58 AM, Colin LeMahieu <colinl at codeaurora.org> wrote: > It might help after adding explicit types where needed and before adding > the opaque pointer type, to change all pointers to a single type in the > existing type system, i8* could work or maybe a weird type that would shake > out any issues like i99*. > I'm not sure this would help

On Tue, Feb 17, 2015 at 1:22 PM, Chris Lattner <clattner at apple.com> wrote: > On Feb 17, 2015, at 9:33 AM, David Blaikie <dblaikie at gmail.com> wrote: > > For some more detail: pointer types (i32*, %foo*, etc) complicate IR >> canonicalization. store + load should be the same instructions given the >> same number of bytes stored to memory, but instead we can

On Mon, Aug 10, 2020 at 5:15 AM Alexey Lapshin <avl.lapshin at gmail.com> wrote: > > Hi Jonas, > > Thank you for the comments, please find my answers below... > > On 06.08.2020 20:39, Jonas Devlieghere wrote: > > Hi Alexey, > > I should've looked at this earlier. I went through the thread again and I've > made some comments, mostly from the dsymutil