human: Given a hyperedge-centered hypergraph: <hypergraph>, where the center hyperedge is induced by one source paper and its member nodes are the cited papers.

Details of the hypergraph:
Center hyperedge (induced by source paper "exorcising spectres with secure compilers"):
  Abstract: Speculative execution has been demonstrated to leak information about execution in case the speculation is ill-informed. This has lead to the Spectre family of attacks (i.e., Spectre v1, v2 and rbr) and the related compiler-inserted countermeasures. Spectre (v1) and the speculative semantics needed to express it has been recently formalised in a number of works, so we have the techniques to formally express a Spectre-like violation. However, the correctness (and security) of compiler-inserted Spectre countermeasures has not been ascertained yet. Even worse, while some of the existing countermeasures seem to be secure, others are known to be insecure and still leave vulnerabilities to Spectre. We want to investigate whether existing compilers are effectively secure against Spectre attacks or not. For this, we build on recent secure compilation theory telling that a compiler is secure when it preserves certain classes of (hyper)properties. In fact, Spectre-like attacks are violations of speculative non-interference, a non-interference-like property, which is a 2-Hypersafety property. We aim to show that certain compiler countermeasures preserve any 2-Hypersafety property and therefore are secure against Spectre. On the other hand, we want to demonstrate that other compilers do not preserve speculative non-interference, and as such they do not defend against Spectre. We believe this is the first step towards talking about compiler security against the whole Spectre family of attacks.

Includes members:
  Member "towards constant time foundations for the new spectre era":
    also connected through other hyperedges:
      - Hyperedge HE-1 (induced by source paper "inspectre breaking and fixing microarchitectural vulnerabilities by formal analysis")
  Member "speculative buffer overflows attacks and defenses":
    also connected through other hyperedges:
      - Hyperedge HE-2 (induced by source paper "bypassing memory safety mechanisms through speculative control flow hijacks")
  Member "spectector principled detection of speculative information flows":
    also connected through other hyperedges:
      - Hyperedge HE-3 (induced by source paper "specusym speculative symbolic execution for cache timing leak detection")
  Member "journey beyond full abstraction exploring robust property preservation for secure compilation":
    also connected through other hyperedges:
      - Hyperedge HE-4 (induced by source paper "why should anyone use colours or syntax highlighting beyond code snippets")
  Member "you shall not bypass employing data dependencies to prevent bounds check bypass":
    also connected through other hyperedges:
      - Hyperedge HE-5 (induced by source paper "context leakage free transient execution")
  Member "spectre returns speculation attacks using the return stack buffer":
    also connected through other hyperedges:
      - Hyperedge HE-6 (induced by source paper "ghostknight breaching data integrity via speculative execution")
  Member "ret2spec speculative execution using return stack buffers":
    also connected through other hyperedges:
      - Hyperedge HE-7 (induced by source paper "ghostknight breaching data integrity via speculative execution")
  Member "a formally verified compiler back end":
    also connected through other hyperedges:
      - Hyperedge HE-8 (induced by source paper "a survey on theorem provers in formal methods")

Question: Please tell me which class the source paper belongs to. The 40 classes are: cs.NA(Numerical Analysis), cs.MM(Multimedia), cs.LO(Logic in Computer Science), cs.CY(Computers and Society), cs.CR(Cryptography and Security), cs.DC(Distributed, Parallel, and Cluster Computing), cs.HC(Human-Computer Interaction), cs.CE(Computational Engineering, Finance, and Science), cs.NI(Networking and Internet Architecture), cs.CC(Computational Complexity), cs.AI(Artificial Intelligence), cs.MA(Multiagent Systems), cs.GL(General Literature), cs.NE(Neural and Evolutionary Computing), cs.SC(Symbolic Computation), cs.AR(Hardware Architecture), cs.CV(Computer Vision and Pattern Recognition), cs.GR(Graphics), cs.ET(Emerging Technologies), cs.SY(Systems and Control), cs.CG(Computational Geometry), cs.OH(Other Computer Science), cs.PL(Programming Languages), cs.SE(Software Engineering), cs.LG(Machine Learning), cs.SD(Sound), cs.SI(Social and Information Networks), cs.RO(Robotics), cs.IT(Information Theory), cs.PF(Performance), cs.CL(Computation and Language), cs.IR(Information Retrieval), cs.MS(Mathematical Software), cs.FL(Formal Languages and Automata Theory), cs.DS(Data Structures and Algorithms), cs.OS(Operating Systems), cs.GT(Computer Science and Game Theory), cs.DB(Databases), cs.DL(Digital Libraries), cs.DM(Discrete Mathematics). Directly output the class name.

gpt: cs.PL(Programming Languages)