Liberty Eiffel - Tasks: task #13320, Make generated C code thread-safe
You are not allowed to post comments on this tracker with your current authentication level.
task #13320: Make generated C code thread-safe
Submitter: | Raphael Mack <ramack> | ||
Submitted: | Wed 10 Sep 2014 08:01:46 PM UTC | ||
Should Start On: | Tue 09 Sep 2014 10:00:00 PM UTC | Should be Finished on: | Tue 09 Sep 2014 10:00:00 PM UTC |
Category: | SmartEiffel | Priority: | 5 - Normal |
Status: | In Progress | Assigned to: | cadrian |
Percent Complete: | 20% | Open/Closed: | Open |
Fixed Release: | None | Planned Release: | None |
Effort: | 0.00 |
Fri 03 Jun 2016 11:52:22 AM UTC, comment #3: |
Paolo Redaelli <Tybor> |
Mon 15 Feb 2016 11:21:43 AM UTC, comment #2: if IPC is the preferred alternative to threading, we'd need this to be non-blocking, indicating the additional need for a message queue library. Can MQ0 be used for that? Is the wrapping complete and validated? |
- <_92048> |
Sun 14 Sep 2014 06:34:59 AM UTC, comment #1: WIP in commits 0f7dcbc, 97ea62c, 119d646, c369ded, and others.
|
Cyril Adrian <cadrian> |
Wed 10 Sep 2014 08:01:46 PM UTC, original submission:
As a starting point, how about just making the generated C code thread-safe? Right now the use of global static variables makes the generated C code unsafe.
|
Raphael Mack <ramack> |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 4 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2014-09-14 | cadrian | Category | None | SmartEiffel | |
Status | None | In Progress | |||
Percent Complete | 0% | 20% | |||
Assigned to | None | cadrian |
Powered by Savane 3.13-f8d8.
Corresponding source code
AFAIK Cyril used ømq for one of his projects.
We haven't put formal checks and tests, yet, I'm going to add them.
Just a suggestion, what approach do you suggest?
1. completely separate executables with their own makefile. Cleaner but harder to integrate into current automatic testing framework
2. forking server and client using PROCESS in cluster exec. Easier but client and server will share the same, common parent process.