Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • M mu-impl-fast
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 40
    • Issues 40
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar

WARNING! Access to this system is limited to authorised users only.
Unauthorised users may be subject to prosecution.
Unauthorised access to this system is a criminal offence under Australian law (Federal Crimes Act 1914 Part VIA)
It is a criminal offence to:
(1) Obtain access to data without authority. -Penalty 2 years imprisonment.
(2) Damage, delete, alter or insert data without authority. -Penalty 10 years imprisonment.
User activity is monitored and recorded. Anyone using this system expressly consents to such monitoring and recording.

To protect your data, the CISO officer has suggested users to enable 2FA as soon as possible.
Currently 2.7% of users enabled 2FA.

  • mu
  • mu-impl-fast
  • Issues
  • #57

Closed
Open
Created Jul 08, 2017 by Isaac Gariano@igariano01Maintainer

Giving a weird name to a function dosn't work

A test I added to test zebus name handling capabilities, which even after my addition of proper mangling, is failing strangely, specifically the test run by pytest tests/test_muc/test_simple.py::test_name which builds the bundle:

.global @-0.a5-1_5 <void>
.const @0 <int<32>> = 0
.funcdef @0-main.func <main_sig>
{
    entry(<int<32>>%1.3 <uptr<uptr<char>>>%-):
        RET @0
}

And creates an executable called test_name with the primordial function 0-main.func.

When trying to compile it produces the following error:

TRACE - Linking boot image...
TRACE - functions: ["0-main.func", "primordial"]
TRACE - extern sources: []
TRACE - output   : test_name
TRACE - copying from "/root/mu-impl-fast/src/runtime/main.c" to "emit/main.c"
INFO - output as "emit/test_name"
INFO - link with "emit/0-main.s"
INFO - link with "emit/primordial.s"
INFO - link with "emit/context.s"
INFO - link with "emit/main.c"
INFO - link with "/root/mu-impl-fast/target/release/libmu.a"
INFO - executing: "clang" "-ldl" "-lrt" "-lm" "-lpthread" "emit/0-main.s" "emit/primordial.s" "emit/context.s" "emit/main.c" "/root/mu-impl-fast/target/release/libmu.a" "-rdynamic" "-o" "emit/test_name"
INFO - ---out---
INFO -
INFO - ---err---
INFO - clang-4.0: error: no such file or directory: 'emit/0-main.s'

Where the name 0-main.func came from is a complete mystery... (it seams to have chopped of the .func part of the functions name, but why??)

Assignee
Assign to
Time tracking