March 2014 - Asg - mailman3.cels.anl.gov

[aesop] #38: bracketed single-line if statements
by aesop 11 May '15

11 May '15

#38: bracketed single-line if statements --------------------------------+------------------------------------------- Reporter: gcdanie@… | Type: defect Status: new | Priority: don't know Component: don't know | Version: Keywords: | --------------------------------+------------------------------------------- When compiling a non-blocking function (e.g., without a __blocking identifier), should that function contain a single line if statement enclosed in brackets (as below), the aesop compiler will error (as below). if (condition) { return something; } aatree.c:79:1: error: stray ‘#’ in program aatree.c:79:7: warning: statement with no effect [-Wunused-value] aatree.c:79:10: error: expected ‘;’ before string constant aatree.c:81:31: error: ‘dir’ undeclared (first use in this function) aatree.c:81:31: note: each undeclared identifier is reported only once for each function it appears in aatree.c: In function ‘__ae_worker_treenode_traverse’: -- Ticket URL: <http://trac.mcs.anl.gov/projects/aesop/ticket/38> aesop <https://trac.mcs.anl.gov/projects/aesop> The Aesop Language

2 3

[aesop] #46: parallelfor2 test failure
by aesop 20 Mar '15

20 Mar '15

#46: parallelfor2 test failure -------------------------+-------------------------------------------------- Reporter: carns | Owner: Type: defect | Status: new Priority: minor | Component: don't know Version: devel branch | Keywords: -------------------------+-------------------------------------------------- The parser/tests/blocking/parallelfor2 test program fails with the following assertion: {{{ parallelfor2: /home/pcarns/working/aesop-devel/build/include/aesop/ae- ctl.h:229: ae_ctl_done: Assertion `refcount >= 0' failed. Aborted (core dumped) }}} -- Ticket URL: <https://trac.mcs.anl.gov/projects/aesop/ticket/46> aesop <https://trac.mcs.anl.gov/projects/aesop> The Aesop Language

1 3

[aesop] #34: Initialization + declaration: invalid reorder
by aesop 30 Sep '14

30 Sep '14

#34: Initialization + declaration: invalid reorder ---------------------------+------------------------------------------------ Reporter: dkimpe | Owner: Type: defect | Status: new Priority: major | Component: code generator Version: git repository | Keywords: ---------------------------+------------------------------------------------ In the following (accepted by the compiler): {{{ ... init_a (); int my_var = call_b (); ... }}} my_var gets moved to the context structure (correct); However, it gets initialized at the beginning of the function, effectively moving {{{call_b}}} before {{{init_a}}} in the example. This can be a very hard to track down bug... Possible solution: disallow behavior in source translator or fix. -- Ticket URL: <https://trac.mcs.anl.gov/projects/aesop/ticket/34> aesop <https://trac.mcs.anl.gov/projects/aesop> The Aesop Language

1 2

[aesop] #26: OSX warnings during build
by aesop 12 Sep '14

12 Sep '14

#26: OSX warnings during build -------------------------------+-------------------------------------------- Reporter: rross@… | Type: defect Status: new | Priority: don't know Component: don't know | Version: Keywords: | -------------------------------+-------------------------------------------- Lots of warnings when building on my OSX box. -- Rob --- make -C src/c-utils GHC parser/ae-blocking-parser CC opcache.o CC aesop.o DEP lookup3.d DEP triton-string.d CC resource.o DEP libev/event.d In file included from ../resource.c:1: ../src/c-utils/libev/ev.h: In function ‘ev_default_loop_uc_’: ../src/c-utils/libev/ev.h:548: warning: nested extern declaration of ‘ev_default_loop_ptr’ DEP libev/ev.d ../resource.c: In function ‘ae_get_stack’: ../resource.c:738: warning: format not a string literal and no format arguments CC hints.o CC libev/ev.o CC libev/event.o CC triton-string.o CC lookup3.o CC ae-ctl.o CC ae-init.o RANLIB libc-utils.a Linking parser/ae-blocking-parser ... ld: warning: could not create compact unwind for _ffi_call_unix64: does not use RBP or RSP based frame AECC src/aefile/aefile.ae AECC src/socket/aesocket.ae AECC resources/resourcebuilder/resourcebuilder.hae AECC resources/thread/aethread.hae AECC resources/timer/timer.hae CC resources/resourcebuilder/resourcebuilder.o CC resources/thread/aethread.o CC resources/timer/timer.o In file included from ../resources/timer/timer.c:14: ../src/c-utils/libev/ev.h: In function ‘ev_default_loop_uc_’: ../src/c-utils/libev/ev.h:548: warning: nested extern declaration of ‘ev_default_loop_ptr’ /usr/include/assert.h:79: warning: previous declaration of ‘__assert_rtn’ was here /usr/include/assert.h:79: warning: previous declaration of ‘__assert_rtn’ was here ../src/aefile/aefile.hae:23: warning: previous declaration of ‘aefile_pwrite’ was here ../src/aefile/aefile.hae:24: warning: previous declaration of ‘aefile_pread’ was here ../src/aefile/aefile.hae:22: warning: previous declaration of ‘aefile_fsync’ was here ../src/aefile/aefile.hae:23: warning: previous declaration of ‘aefile_fdatasync’ was here ../src/aefile/aefile.ae: In function ‘__ae_worker_aefile_fdatasync’: ../src/aefile/aefile.ae:88: warning: nested extern declaration of ‘fdatasync’ ../src/aefile/aefile.ae: At top level: ../src/aefile/aefile.hae:25: warning: previous declaration of ‘aefile_ftruncate’ was here ../src/aefile/aefile.hae:25: warning: previous declaration of ‘aefile_unlink’ was here /usr/include/assert.h:79: warning: previous declaration of ‘__assert_rtn’ was here /usr/include/assert.h:79: warning: previous declaration of ‘__assert_rtn’ was here /usr/include/string.h:172: warning: previous declaration of ‘swab’ was here /usr/include/stdlib.h:218: warning: previous declaration of ‘mkstemp’ was here /usr/include/stdlib.h:217: warning: previous declaration of ‘mktemp’ was here /usr/include/stdlib.h:235: warning: previous declaration of ‘setkey’ was here /usr/include/stdlib.h:341: warning: previous declaration of ‘valloc’ was here /usr/include/stdlib.h:340: warning: previous declaration of ‘suboptarg’ was here /usr/include/stdlib.h:206: warning: previous declaration of ‘getsubopt’ was here /usr/include/assert.h:79: warning: previous declaration of ‘__assert_rtn’ was here /usr/include/pthread.h:400: warning: previous declaration of ‘pthread_kill’ was here /usr/include/pthread.h:406: warning: previous declaration of ‘pthread_sigmask’ was here /usr/include/unistd.h:710: warning: previous declaration of ‘mknod’ was here ../src/c-utils/libev/ev.h: In function ‘ev_default_loop_uc_’: ../src/c-utils/libev/ev.h:548: warning: nested extern declaration of ‘ev_default_loop_ptr’ ../src/socket/aesocket.ae: At top level: ../src/socket/aesocket.hae:79: warning: previous declaration of ‘aesocket_ready’ was here ../src/socket/aesocket.hae:45: warning: previous declaration of ‘aesocket_accept’ was here ../src/socket/aesocket.hae:56: warning: previous declaration of ‘aesocket_read’ was here ../src/socket/aesocket.hae:67: warning: previous declaration of ‘aesocket_write’ was here RANLIB lib/libaesop.a mcswl174:build rross$ -- Ticket URL: <http://trac.mcs.anl.gov/projects/aesop/ticket/26> aesop <https://trac.mcs.anl.gov/projects/aesop> The Aesop Language

1 1

[aesop] #22: overriding CFLAGS in make or configure causes build to fail.
by aesop 12 Sep '14

12 Sep '14

#22: overriding CFLAGS in make or configure causes build to fail. ---------------------------+------------------------------------------------ Reporter: dkimpe | Owner: Type: defect | Status: new Priority: minor | Component: build system Version: git repository | Keywords: ---------------------------+------------------------------------------------ Configuring aesop using CFLAGS="-O2" (i.e. ./configure CFLAGS="-O2") or issuing make CFLAGS="-O2" causes the build to fail. One reason is that it overrides the -I needed to find aesop.h. This most likely is a bug in Makefile.in and/or aecc -- Ticket URL: <http://trac.mcs.anl.gov/projects/aesop/ticket/22> aesop <https://trac.mcs.anl.gov/projects/aesop> The Aesop Language

1 2

Weekly report
by guoxinl＠clemson.edu 16 Jun '14

16 Jun '14

Dear all, In this week, we analyzed the test results of a proximity-aware file replication method, which copies data to the hubs of all request paths in a P2P file storage. We compared the performance with other methods, which replicates files onto client-side, server-side and hot paths. In this week, we will study a replication method based on a hybrid structure with both structured and unstructured P2P overlay in order to achieve a better tradeoff between replication overhead and request latencies. Guoxin Liu PHD Candidate ECE, Clemson University

2 2

Project-related papers and presentations at workshops and conferences
by Ward, Lee 14 Apr '14

14 Apr '14

Time for a reminder… For me as well, since I keep forgetting too :( If you have a LANL contract then all papers and presentations for publication *must* go through a review and approval process at least 45 days before you submit them; Note, "submit" not publish. This means the final draft of the paper, not the first draft. You send those final drafts to Gary Grider, ggrider(a)lanl.gov, and Paul Iwanchuck, pniwanc(a)lanl.gov, and pretty please CC a copy to Rob and myself so we know what's going on and can use material in the yearly review the sponsor requires. Also, please put a copy of that draft on the wiki since I rely on it heavily for source material and context. Really, the final draft 45 days before submission. --Lee

2 1

Client API discussion
by Dries Kimpe 31 Mar '14

31 Mar '14

Hi, I'd like to reserve the usual time on Mon 3/16 to discuss our shared client API. We have about one quarter left to adopt a shared client API, and while we have a good start (the one we designed a long time ago) we all found some things that are not as nice or efficient as they could be. Some things just need to be clarified. Some examples: - the probe+read race condition/inefficiency. - can update id/version decrease? - is it valid to write a 0-version (or can only reset do that)? ... So, I'd like to dedicate 3/16, 3-4PM CST (usual concall number) to review the API. This will mainly be relevant for the Sirocco/Triton teams (as well as TAMU, who can share their experiences implementing the posix client on top of this API). For preparation, I would ask that everybody tries to prepare a list of issues we can go over in the call. Please confirm if you can make the call (which should be no problem, since if I recall correctly, we were going to keep this time open every week even if the call was only once a month). Thanks, Dries

5 9

ANL Weekly Status - 20130331
by Harms, Kevin N. 31 Mar '14

31 Mar '14

Simulation: - We continue to polish our rebuild paper to be sent for final review. - Work continues on our epidemic modeling and testing deliverable. (experiments with different failure modes) kevin

1 0

Weekly report
by guoxinl＠clemson.edu 31 Mar '14

31 Mar '14

Dear all, In the last week, we studied how to efficiently locate the data being stored anywhere in a single location, such as a rack or a cluster. We aimed to distribute the storage of metadata into different servers in order to support an efficient access (read and write). Best Regards! Guoxin Liu PHD Candidate ECE, Clemson University

1 0