search for: endedness

...0:09 AM, James Courtier-Dutton <james.dutton at gmail.com> wrote: > My guess is that this is a missed optimization, but in real life, all > projects i have worked fix this in the C or C++ code using macros that > change what instructions are used based on target platform and its > endedness. One reason for writing code like this, i.e. explicitly spelling out the accesses to the individual bytes, would be to allow compile-time evaluation of the fragment in the D programming language, where arbitrarily reinterpreting memory is not supported (although integer->integer pointer casts m...

I've done a decent size update of the OpenSSH portable from the upstream tree. There is an AES upgrade that needs to take place, but I need people to test and tell me what endedness changes need to be applied (if any). Attached is the patch. It is geared towards the latter snapshots..Unsure how it will patch (if at all) against 2.9pX series. http://www.eviladmin.org/~mouring/openssh/aes.patch Thanks. - Ben "This is dark day in humanity."

...oad based on the IR semantics, or is this just a missed optimization > opportunity? > My guess is that this is a missed optimization, but in real life, all projects i have worked fix this in the C or C++ code using macros that change what instructions are used based on target platform and its endedness. James -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20131028/0b9609a0/attachment.html>

The following piece of IR is a fixed point for opt -std-compile-opts/-O3: --- target datalayout = "e-p:64:64:64-S128-i1:8:8-i8:8:8-i16:16:16-i32:32:32-i64:64:64-f16:16:16-f32:32:32-f64:64:64-f128:128:128-v64:64:64-v128:128:128-a0:0:64-s0:64:64-f80:128:128-n8:16:32:64" target triple = "x86_64-unknown-linux-gnu" ; Function Attrs: nounwind readonly define i32 @get32Bits(i8*

....dutton at gmail.com> wrote: > > My guess is that this is a missed optimization, but in real life, > > all > > projects i have worked fix this in the C or C++ code using macros > > that > > change what instructions are used based on target platform and its > > endedness. > > One reason for writing code like this, i.e. explicitly spelling out > the accesses to the individual bytes, would be to allow compile-time > evaluation of the fragment in the D programming language, where > arbitrarily reinterpreting memory is not supported (although > integ...

...: > > > My guess is that this is a missed optimization, but in real life, > > > all > > > projects i have worked fix this in the C or C++ code using macros > > > that > > > change what instructions are used based on target platform and its > > > endedness. > > > > One reason for writing code like this, i.e. explicitly spelling out > > the accesses to the individual bytes, would be to allow compile-time > > evaluation of the fragment in the D programming language, where > > arbitrarily reinterpreting memory is not suppor...

Well, this is a bit stronger than a proposal; this is "what I plan to do unless people see obvious flaws I missed"... The text comment header is the second (of three) header packets that begin a Vorbis bitstream. It is meant for short, text comments, not arbitrary metadata; arbitrary metadata will be put in a metadata stream, likely an XML stream type. We've discussed this in

I've done a decent size update of the OpenSSH portable from the upstream tree. There is an AES upgrade that needs to take place, but I need people to test and tell me what endedness changes need to be applied (if any). Attached is the patch. It is geared towards the latter snapshots..Unsure how it will patch (if at all) against 2.9pX series. Thanks. - Ben "This is dark day in humanity." Index: cipher.c ============================================================...