Topic for #qi-hardware is now Copyleft hardware - http://qi-hardware.com | hardware hackers join here to discuss Ben NanoNote, atben / atusb 802.15.4 wireless, and other community driven hw projects | public logging at http://en.qi-hardware.com/irclogs
urandom__ has quit [Quit: Konversation terminated!]
bzb has quit [Quit: Leaving]
bzb has joined #qi-hardware
emeb has quit [Quit: Leaving.]
panda|x201 has joined #qi-hardware
DocScrutinizer05 has quit [Disconnected by services]
DocScrutinizer06 has joined #qi-hardware
megha has quit [Ping timeout: 256 seconds]
bzb has quit [Quit: Leaving]
megha has joined #qi-hardware
wolfspra1l has joined #qi-hardware
jekhor has joined #qi-hardware
wolfspraul has quit [Ping timeout: 248 seconds]
megha has quit [Quit: WeeChat 0.3.9.2]
jekhor has quit [Ping timeout: 248 seconds]
panda|x201 has quit [Remote host closed the connection]
LunaVorax has joined #qi-hardware
megha has joined #qi-hardware
LunaVorax has quit [Ping timeout: 260 seconds]
panda|x201 has joined #qi-hardware
<whitequark> wpwrak: is there even such a thing as -O9?
<whitequark> -O3 should be the last one
jluis has joined #qi-hardware
LunaVorax has joined #qi-hardware
<wpwrak> well, it's an implementation-independent way of asking the compiler to give everything it has :)
uwe_ has quit [Read error: Operation timed out]
uwe_ has joined #qi-hardware
<whitequark> wpwrak: I once committed a mistake of using -O10 for much the same reason
<whitequark> obviously it ignored the zero, so...
xiangfu has joined #qi-hardware
panda|x201 has quit [Ping timeout: 245 seconds]
rz2k has joined #qi-hardware
<Fallenou> ahah
xiangfu has quit [Quit: leaving]
xiangfu has joined #qi-hardware
<whitequark> the yet-to-be-released LLVM linker can emit files in YAML format (as an alternative to ELF, COFF, ...)
<whitequark> like this: http://pastie.org/5827976
<whitequark> I find it that more Unix[-way] tools should be able to emit data in a format which is both machine-parseable and human-readable.
jekhor has joined #qi-hardware
dandon has quit [Ping timeout: 252 seconds]
dandon_ has joined #qi-hardware
dandon_ is now known as dandon
jekhor has quit [Ping timeout: 246 seconds]
jekhor has joined #qi-hardware
LunaVorax has quit [Ping timeout: 260 seconds]
urandom__ has joined #qi-hardware
LunaVorax has joined #qi-hardware
<wpwrak> (yaml) looks like a nice format. not xml ;-) ("oh, but it's all text, so it's very human-readable")
jekhor has quit [Ping timeout: 245 seconds]
<whitequark> wpwrak: yup. it's kinda popular in ruby and python, especially ruby
<whitequark> and it allows for a portable way to serialize complex objects
<whitequark> i.e. you need to output it as text, but you can define which procedure your deserializer must use
<whitequark> so there's no need to pass dates in ISO8601 strings and fuzzy-match them on the receiving end :/
<whitequark> as json does.
urandom__ has quit [Quit: Konversation terminated!]
kuribas has joined #qi-hardware
bzb has joined #qi-hardware
bzb has quit [Quit: Leaving]
erikkugel has joined #qi-hardware
kanzure has quit [Ping timeout: 248 seconds]
kanzure has joined #qi-hardware
rzk|2 has joined #qi-hardware
rz2k has quit [Ping timeout: 248 seconds]
kilae has joined #qi-hardware
DocScrutinizer06 is now known as DocScrutinizer05
erikkugel has left #qi-hardware [#qi-hardware]
LunaVorax has quit [Ping timeout: 260 seconds]
emeb has joined #qi-hardware
rzk|2 has quit []
<wpwrak> hmm, seems that there's a pretty large set of potential optimization bugs (all related to "volatile") behind the critter i found. http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56098
wpwrak has quit [Read error: Connection reset by peer]
wpwrak has joined #qi-hardware
<whitequark> wpwrak: don't use volatile, it's broken by design
kristianpaul has joined #qi-hardware
<wpwrak> naw, there are fairly reasonable conventions in place that give volatile useful and predictable behaviour beyond what ANSI C specifies
<wpwrak> but i would agree that, as far as the standard is concerned, it's broken :)
<whitequark> well you have nice atomics in C++11
<whitequark> and maybe you can also have them in C11, I'm not sure
<kristianpaul> phew new psu :-)
<wpwrak> kristianpaul: fan reached expiration date ? :)
<whitequark> but from a quick peek, it's far more opaque than the stuff found in C++11
<whitequark> you might or might not find that useful.
<wpwrak> gcc has some builtins beyond sync ... lemme check ...
<whitequark> yeah. you probably need __ATOMIC_SEQ_CST
<whitequark> which, on one hand, will insert memory barriers in the compiler, because that's correct semantics
<whitequark> but on other one, the CPU inserts them by itself when you fiddle with I/O memory, so that theoretically shouldn't slow you down
<wpwrak> but i find them a bit heavy for what i'm looking for here. my goal is to have a "nice" syntax. and the semantics of volatile allow me to get this, even if it may not be optimally efficient.
xiangfu has quit [Ping timeout: 245 seconds]
<wpwrak> i wouldn't be so sure about the CPU inserting anything for you. some do, others don't ...
<whitequark> wpwrak: well, if your CPU has I/O memory and volatile works with it, it does
<whitequark> it either does insert the correct barriers or does not have out-of-order execution, that is.
xiangfu has joined #qi-hardware
<whitequark> the latter is probably true for Jz4740
<whitequark> (considering it doesn't have SMP anyway)
<wpwrak> ah, you meant OO. i thought of bus locks.
<whitequark> yup, you got to flush the store reordering buffer and serialize the pipeline
<whitequark> hah. just learned that LLVM can compile code for VLIW DSP targets
<whitequark> which is quite impressive if you'd ask. http://en.wikipedia.org/wiki/Qualcomm_Hexagon
<whitequark> eg it automatically recognizes induction variable when it postincrements over some pointer and converts it to a hardware loop
<wpwrak> putting all that analysis it already does for other reasons to good use :)
<whitequark> that is very much true
<roh> i think the hexagon stuff is quite new
<roh> afaik thats qualcomms bb arch
<whitequark> roh: yes, and it's somewhat WIP
<whitequark> e.g. the hardware loop stuff is actually a patch on its ML
<whitequark> but still
<roh> nice. sure. does a disassm exist also?
<whitequark> roh: lemme check
<roh> need to run.. bbl
<kristianpaul> wpwrak: dust made its work too...
<whitequark> roh: looks like it's not the case
xiangfu has quit [Ping timeout: 252 seconds]
megha has quit [Ping timeout: 264 seconds]
<wpwrak> kristianpaul: time for someone to develop fans without mechanical bearings :)
<whitequark> roh: but gnu toolchain, which is also available, does include a disassembler in objdump, as usual
<wpwrak> well, make that _inexpensive_ fans. i'm sure there are some that work very nicely and cost a ton of money.
kuribas has quit [Quit: ERC Version 5.3 (IRC client for Emacs)]
<kristianpaul> wpwrak: ;)
<whitequark> make fans with magnetic levitation
megha has joined #qi-hardware
<wpwrak> yeah, that's roughly what i was thinking of
<wpwrak> 8 USD. hmm. and look suspiciously like traditional fans.
<wpwrak> ``According to Sunon, this kind of fan has a life-span of 50,000 hours at “room temperature”''. that's less than for conventional bearings. http://www.hardwaresecrets.com/printpage/Anatomy-of-Computer-Fans/1039
<wpwrak> maybe a bit more tech needs to be thrown at that problem. such a fan should in theory live forever. you could seal it completely, so if it gets dirty, rinse off the worst, then toss it into the dish washer.
<wpwrak> then all you get would be abrasion by particles floating in the gaps, plus any aging of materials. both should be negligible. of course, such a design may be a bit heavy ...
<wpwrak> or just wait for quantum physics to finally crack that theory of everything and then use a directed gravitational field to move that air. (with appropriate dampening, of course)
bzb has joined #qi-hardware
kilae has quit [Quit: ChatZilla 0.9.89 [Firefox 18.0.1/20130116073211]]
uwe__ has joined #qi-hardware
bzb has quit [*.net *.split]
uwe_ has quit [*.net *.split]
urandom__ has joined #qi-hardware
rz2k has joined #qi-hardware
<whitequark> I also find it quite hilarious that Qualcomm open-sourced their DSP effort
<whitequark> given all that stuff about "let's only allow GPL plugins so evil proprietary vendors won't write them". and qualcomm for sure fits the definition of an evil proprietary vendor.
<whitequark> not only opensourced, but they even do it within the usual community contribution process
<whitequark> and not just post patchbombs no one could make sense of
jekhor has joined #qi-hardware
paroneayea has quit [Read error: Connection reset by peer]
paroneayea has joined #qi-hardware
LunaVorax has joined #qi-hardware
paroneayea has quit [Remote host closed the connection]
paroneayea has joined #qi-hardware
viric_ has joined #qi-hardware
viric has quit [Ping timeout: 276 seconds]
<wpwrak> whitequark: breaking news: scientists have detected strong evidence that developers are able to learn, if given enough time and mistakes. ;-)
<whitequark> wpwrak: ... however, the same couldn't be said about managers ;)
<wpwrak> ... or the beancounters at finances
LunaVorax has quit [Ping timeout: 260 seconds]
paroneayea has quit [Remote host closed the connection]
<whitequark> indeed. "beancounters", I like that word
<wpwrak> one theory is that managers fulfill an orwellian role to maintain a good team spirit among the developers, acting as everyone's external inscrutable enemy
<qi-bot> [commit] Werner Almesberger: ubb-la/Makefile (CFLAGS): use more specific -O9 -fno-tree-cselim (master) http://qi-hw.com/p/ben-blinkenlights/09de245
<qi-bot> [commit] Werner Almesberger: ubb-patgen/Makefile (CFLAGS): use more specific -O9 -fno-tree-cselim (master) http://qi-hw.com/p/ben-blinkenlights/a947b5e
paroneayea has joined #qi-hardware
jekhor has quit [Read error: Operation timed out]
paroneayea has quit [Remote host closed the connection]
paroneayea has joined #qi-hardware
rz2k has quit [Read error: Connection reset by peer]