search for: unportable

...*)0x00001000 > > which is horrible. The drivers I have seen can't work that way because they are written to cover more than one specific machine. As soon as you go anywhere near an IO abstraction, this doesn't apply anymore. As such, I think this feature primarily helps making ugly, unportable code differently ugly, unportable code. Joerg

Hi all It would be nice to add support for placing globals at fixed addresses in memory. For example, low level driver code tends to contain things like this *(int*)0x00001000 which is horrible. Alternatively people are using linker scripts and assembly hacks to put symbols at fixed addresses. I propose we add first class support to this in the compiler. Like addrspace(#) we should have

Hello all, As of now, all LLVM and Clang tests have been updated/addressed to run under the new/experimental pass manager (at least the ones that failed when using the new PM). For those who aren't aware of what the new pass manager (PM) is, the tl;dr is that this will serve as a replacement for the legacy PM, and promises faster build times by restructuring how passes are run over IR units.

...eryone, I am an avid Sweave user and I am trying to pretty print floating point numbers for latex output. For example in my document, I would like: 4.2\cdot 10^-{8} Instead of: 4.2e-08 The Hmisc package has a nice function for doing this- but Hmisc has a ton of dependencies and has proved very unportable to the various machines I work on. So, I set out to write my own function that just uses basic R commands, it looks like this: latexNum <- function (x,dig=4,sci=T) { x <- format(x,digits=dig,scientific=sci) x <- gsub("e\\+00","",x) x <- gsu...

Just my two cents: Anyone thought of asking Red Hat to use documentation? I think they are getting much from the community so to copy public accessible documentation when permitted by RH could be an easy way. Why not giving that a try? Am 18. Januar 2015 20:56:59 MEZ, schrieb Darr247 <darr247 at gmail.com>: >On 18 January 2015 @19:07 zulu, Mark LaPierre wrote: >> good at C or C++

Hello everybody, My partner and I want to make a parser generator that will generate LLVM bitcode directly so that it can use libraries compiled in any LLVM-based language. Unfortunately we are running into some problems with dependencies on libc since it is different on every operating system. The Mac, for example, defines stdin as a macro in stdio.h. Is there going to be a collection of

I think so far most individual projects have their own statistics on build time/performance impact on switching to the new PM, but I agree that there should at least be one place that people can reference on the impact. On Fri, Aug 2, 2019 at 1:14 PM Philip Reames <listmail at philipreames.com> wrote: > Thanks for all the hard work that went into getting it here. > > +1 > >

...hich is horrible. > > The drivers I have seen can't work that way because they are written to > cover more than one specific machine. As soon as you go anywhere near an > IO abstraction, this doesn't apply anymore. As such, I think this > feature primarily helps making ugly, unportable code differently ugly, > unportable code. Your argument appears to be that this feature would have little use to you. Noted, I guess. We've spoken to several people who do write drivers and other code like the above, and they seem pretty enthusiastic about the idea. If you have input abou...

I believe a good amount of them (if not most of them) have already been ported! Off the top of my head, I remember that asan, tsan, msan, hwasan, the kernel santizers, and sancov have been ported. I don't think ubsan has been ported yet though. You can also check if other passes you need run under the new PM by checking PassRegistry.def. On Fri, Aug 2, 2019, 14:20 Jordan Rupprecht

On 2/28/16, Linus Torvalds <torvalds at linux-foundation.org> wrote: > The fact is, undefined compiler behavior is never a good idea. Not for > serious projects. Actually, undefined behavior is essential for serious projects, but not for the reasons mentioned. If the language has no undefined behavior, then from the compiler's view, there is no such thing as a bad program. All

...---------------------------------------------------------- typedef unsigned long uint4; ---------------------------------------------------------------------- which on an LP64 system is a lie. If uint4 is used on disk (and it's used in the btree implementation) then it would make the databases unportable, which probably isn't a good idea (unless we already have endianness issues, although even there, an ILP32 and an LP64 process on the same machine should really be able to share databases, although I haven't checked for alignment problems). I'm also not sure why quartz_types.h / flint_...

...it finds inefficiently compressed datasets. With 'bzip2' and 'xz' compression having been available since R 2.10.0, there is no excuse for not using them. Why isn't a note enough for this? Generally speaking, warnings are for things that are dangerous, or unsafe, or unportable, or for anything that could potentially cause trouble. I don't see how using gzip instead of bzip2 or xz could fall into that category (and BTW gzip is the default for save() and for 'R CMD build' resave-data feature). The problem is that bzip2 and xz compressions are slower and also r...

...;re willing to make some concessions to broken clients, an inability to speak TCP correctly is well outside what I consider sensible, particularly given that it will degrade icecast's performance for working clients (you remain welcome, of course, to hack up your local copy). It's also very unportable. Mike

...ts MIDI devices properly allowing WINE (using alsa or OSS interfaces) to feed it the correct devices. It detects audio devices by looking for drivers in the windows directory. How do I know? It finds a Delta44 asio driver even though I do not have the card, just the file. This is a very bad and unportable approach, obviously.

On 01/19/2015 10:51 AM, Tim wrote: > Just my two cents: Anyone thought of asking Red Hat to use > documentation? I think they are getting much from the community so > to copy public accessible documentation when permitted by RH could be > an easy way. > > Why not giving that a try? There's no need to ask them, they've already given permission: > Copyright ? 2014

...ve tools. - Fixed issue with opening relative paths as a mail file. Bug reported by Ian P. Christian. - Fixed MAC OSX compile problem. Turns out the extern modifier was missing at multiple places. Bug reported by Edgar Fuss. - Fixed Solaris compile problem: removed unecessary and unportable linker flags that caused compile to fail. Bug reported by Andres Yacopino. The release is available as follows: http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-sieve-0.1.4.tar.gz http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-sieve-0.1.4.tar.gz.sig Have fun testing the new release and...

...ve tools. - Fixed issue with opening relative paths as a mail file. Bug reported by Ian P. Christian. - Fixed MAC OSX compile problem. Turns out the extern modifier was missing at multiple places. Bug reported by Edgar Fuss. - Fixed Solaris compile problem: removed unecessary and unportable linker flags that caused compile to fail. Bug reported by Andres Yacopino. The release is available as follows: http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-sieve-0.1.4.tar.gz http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-sieve-0.1.4.tar.gz.sig Have fun testing the new release and...

Citeren Arnaud Quette <aquette.dev op gmail.com>: > Date: Thu, 09 Dec 2010 14:01:14 +0000 > Subject: svn commit r2726 - in branches/windows_port: common drivers include > Author: fbohe-guest > Date: Thu Dec 9 14:01:07 2010 > New Revision: 2726 > URL: http://trac.networkupstools.org/projects/nut/changeset/2726 > > Log: > More work on serial drivers. > Still

Hi All I have just published a module that synchronises users and groups from Active Directory into a Puppet manifest, which can then be rolled out to subscribed agents/workstations. The module maintains generated uids and gids in an SQLite database. It has only been tested on Puppet Enterprise 2.6.1 and RHEL 6.3 so far, at my end. The module is called lpep and you can view it at

...In most cases it would, in my opinion, enhance icecasts' performance, since the optimum TCP packet size is being used. CORK would normally result in a more stable data throughput (because each packet is filled to max) using less bandwidth (due to minimizing overhead). > It's also very unportable. It is, that's why my first proposal was to incorporate it as a ./configure option. That way you can leave the default the way it is now, but give end users the option of using it. However i will cleanup the patch for distribution and then sent it to those who requested it. I hope you'll...