From: AUGUSTO VEGA <ajvega@us.ibm.com>
To: "conferences@newsmaster.tgc.com" <conferences@newsmaster.tgc.com>,
"contiki-developers@lists.sourceforge.net"
<contiki-developers@lists.sourceforge.net>,
"cphc-conf@jiscmail.ac.uk" <cphc-conf@jiscmail.ac.uk>,
"csc@lists.purdue.edu" <csc@lists.purdue.edu>,
"DAI-List@mcc.com" <DAI-List@mcc.com>,
"discuss@ieeetcsc.org" <discuss@ieeetcsc.org>,
"distributed-computing-announce@datasys.cs.iit.edu"
<distributed-computing-announce@datasys.cs.iit.edu>,
"editor@hpcwire.com" <editor@hpcwire.com>,
"end2end-china@netarchlab.tsinghua.edu.cn"
<end2end-china@netarchlab.tsinghua.edu.cn>,
"grideditor@gridtoday.com" <grideditor@gridtoday.com>,
"GRUPO@gsd.inesc-id.pt" <GRUPO@gsd.inesc-id.pt>,
"hpc-announce@mcs.anl.gov" <hpc-announce@mcs.anl.gov>,
"icec@listserver.tue.nl" <icec@listserver.tue.nl>,
"info@autonomic-communication.org"
<info@autonomic-communication.org>,
"INVESTIGADORES@inesc-id.pt" <INVESTIGADORES@inesc-id.pt>,
"iot-edge-cloud@comsoc.org" <iot-edge-cloud@comsoc.org>,
"mmb@ira.uka.de" <mmb@ira.uka.de>,
"multicomm@comsoc.org" <multicomm@comsoc.org>,
"NGN@jiscmail.ac.uk" <NGN@jiscmail.ac.uk>,
"performance@merlot.usc.edu" <performance@merlot.usc.edu>,
"planning@asu.edu" <planning@asu.edu>,
"podc-related@acm.org" <podc-related@acm.org>,
"publicity@hipeac.net" <publicity@hipeac.net>,
"remarks@psc.edu" <remarks@psc.edu>,
"SIGCOMM-MEMBERS@acm.org" <SIGCOMM-MEMBERS@acm.org>,
"sigcomm@postel.org" <sigcomm@postel.org>,
"sigmetrics-bb@merlot.usc.edu" <sigmetrics-bb@merlot.usc.edu>,
"sigplan-l@acm.uiuc.edu" <sigplan-l@acm.uiuc.edu>,
"SIGSIM@acm.org" <SIGSIM@acm.org>,
"socinfo@cs.tut.fi" <socinfo@cs.tut.fi>,
"spectrum-webmaster@ieee.org" <spectrum-webmaster@ieee.org>,
"storage-research-list@ece.cmu.edu"
<storage-research-list@ece.cmu.edu>,
"tccc-announce@comsoc.org" <tccc-announce@comsoc.org>,
"tccn@comsoc.org" <tccn@comsoc.org>,
"tcsc@cse.stfx.ca" <tcsc@cse.stfx.ca>,
"tfcc@clustercomputing.org" <tfcc@clustercomputing.org>,
"uksim@glam.ac.uk" <uksim@glam.ac.uk>,
"virtualization@lists.linux-foundation.org"
<virtualization@lists.linux-foundation.org>,
"webmaster@ncsa.uiuc.edu" <webmaster@ncsa.uiuc.edu>,
"hpc-announce-bounces@mcs.anl.gov"
<hpc-announce-bounces@mcs.anl.gov>,
Socinfo <socinfo-bounces@lists.tuni.fi>,
"fpga-list-bounces@mailman.sydney.edu.au"
<fpga-list-bounces@mailman.sydney.edu.au>
Subject: IEEE/ACM 51st International Symposium on Computer Architecture (ISCA 2024)
Date: Fri, 10 May 2024 18:12:59 +0000 [thread overview]
Message-ID: <PH0PR15MB4448B74C1DD9903472553359E5E72@PH0PR15MB4448.namprd15.prod.outlook.com> (raw)
*********************************************************************************
ISCA 2024 - BUENOS AIRES, ARGENTINA - CALL FOR PARTICIPATION
*********************************************************************************
===> Early-Registration Deadline: May 13, 2024
===> Location: Buenos Aires (Argentina)
*********************************************************************************
The International Symposium on Computer Architecture (ISCA) is the premier
forum for new ideas and experimental results in computer architecture. The
conference seeks particularly forward-looking and novel submissions.
In 2024, the 51st edition of ISCA will be held in Buenos Aires, Argentina,
at the Hilton Buenos Aires during June 29 - July 3, 2024.
This is a historic event as ISCA will be held in Latin America for the first
time ever. Let’s make history together!
For more details on ISCA 2024, please visit the main conference website at:
https://iscaconf.org/isca2024/
*********************************************************************************
next reply other threads:[~2024-05-10 18:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-10 18:12 AUGUSTO VEGA [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-05-10 16:07 IEEE/ACM 51st International Symposium on Computer Architecture (ISCA 2024) Augusto Vega
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=PH0PR15MB4448B74C1DD9903472553359E5E72@PH0PR15MB4448.namprd15.prod.outlook.com \
--to=ajvega@us.ibm.com \
--cc=DAI-List@mcc.com \
--cc=GRUPO@gsd.inesc-id.pt \
--cc=INVESTIGADORES@inesc-id.pt \
--cc=NGN@jiscmail.ac.uk \
--cc=SIGCOMM-MEMBERS@acm.org \
--cc=SIGSIM@acm.org \
--cc=conferences@newsmaster.tgc.com \
--cc=contiki-developers@lists.sourceforge.net \
--cc=cphc-conf@jiscmail.ac.uk \
--cc=csc@lists.purdue.edu \
--cc=discuss@ieeetcsc.org \
--cc=distributed-computing-announce@datasys.cs.iit.edu \
--cc=editor@hpcwire.com \
--cc=end2end-china@netarchlab.tsinghua.edu.cn \
--cc=fpga-list-bounces@mailman.sydney.edu.au \
--cc=grideditor@gridtoday.com \
--cc=hpc-announce-bounces@mcs.anl.gov \
--cc=hpc-announce@mcs.anl.gov \
--cc=icec@listserver.tue.nl \
--cc=info@autonomic-communication.org \
--cc=iot-edge-cloud@comsoc.org \
--cc=mmb@ira.uka.de \
--cc=multicomm@comsoc.org \
--cc=performance@merlot.usc.edu \
--cc=planning@asu.edu \
--cc=podc-related@acm.org \
--cc=publicity@hipeac.net \
--cc=remarks@psc.edu \
--cc=sigcomm@postel.org \
--cc=sigmetrics-bb@merlot.usc.edu \
--cc=sigplan-l@acm.uiuc.edu \
--cc=socinfo-bounces@lists.tuni.fi \
--cc=socinfo@cs.tut.fi \
--cc=spectrum-webmaster@ieee.org \
--cc=storage-research-list@ece.cmu.edu \
--cc=tccc-announce@comsoc.org \
--cc=tccn@comsoc.org \
--cc=tcsc@cse.stfx.ca \
--cc=tfcc@clustercomputing.org \
--cc=uksim@glam.ac.uk \
--cc=virtualization@lists.linux-foundation.org \
--cc=webmaster@ncsa.uiuc.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).