September 2013 - 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

[aesop] #48: set up automated Aesop tests in Jenkins
by aesop 23 Oct '13

23 Oct '13

#48: set up automated Aesop tests in Jenkins ----------------------------+----------------------------------------------- Reporter: carns | Owner: Type: feature request | Status: new Priority: critical | Component: build system Version: devel branch | Keywords: ----------------------------+----------------------------------------------- We should add Aesop to MCS's Jenkins test environment for automatic regression testing. The aesop tests are sequential and do not require any MPI or job scheduling environment. Testing can focus on the devel branch until it is merged back to trunk. -- Ticket URL: <https://trac.mcs.anl.gov/projects/aesop/ticket/48> aesop <https://trac.mcs.anl.gov/projects/aesop> The Aesop Language

2 2

[aesop] #20: Provide some debugging helper functions for aesop
by aesop 23 Oct '13

23 Oct '13

#20: Provide some debugging helper functions for aesop ---------------------------+------------------------------------------------ Reporter: dkimpe | Owner: Type: enhancement | Status: new Priority: minor | Component: aesop functions Version: git repository | Keywords: ---------------------------+------------------------------------------------ - would be nice if we had a function to poke at aesop and dump a list of what contexts are running, what function they are in, etc. - the problem right now is if you stop an aesop program in gdb you don't see anything helpful; it is usually in the event loop - could trigger with function call, signal, rpc, or whatever -- Ticket URL: <http://trac.mcs.anl.gov/projects/aesop/ticket/20> aesop <https://trac.mcs.anl.gov/projects/aesop> The Aesop Language

1 1

SSM test status update
by Seok Bae Yun 30 Sep '13

30 Sep '13

HI, We are modifying correctness tests and regression test for the new interface functions for infiniband plug-in given by software developers. The test coverage will be exactly the same with tcp plug-in. Best regards, Seok Bae Yun

1 0

TAMU Update
by Gim Jongmin 30 Sep '13

30 Sep '13

Dear All, I apologize for the late update. For last week, I wrote code for data structure based on PVFS. Most functions related with metadata and marshalling/unmarshalling have been modified, and I tested it with modifying "write" function to check whether data placement works well or not. I traced the data placement with GDB and it looks to be working now. Most APIs does not follow this design yet. Sincerely, Jongmin -- Jongmin Gim Post-Doctoral Research Associate Dept. of Elecrical and Computer Enginerring Texas A&M University 333D Wisenbaker College Station, TX 77843-3259 Phone: 979-587-8311

1 0

weekly update
by jingxuan 30 Sep '13

30 Sep '13

Hi,all, Last week, I have modified our policy example about posix access control, and I am going though the shibboleth details to try to find the way to integrate xacml policy authorization and authentication. I will also have the qualify exam in October 14, so research will go on after that. Jingxuan SUN Holcombe Department of Electrical and Computer Engineering Clemson University Tel:864-643-8210 Email: jingxus(a)g.clemson.edu

1 0