assembly | build tool to assemble client side javascript projects | Runtime Evironment library

The functions Hash_Inline and Hash_FunctionCall are not equivalent:

• The first statement in Hash_Inline rotates by 1, but in Hash_FunctionCall it rotates by curIndex.
• For RotateLeft you may have probably meant:

Check your target framework and language version in your .csproj file. You should find something like:

You left out a : to delimit the empty outputs section. So "S"(ystr) is an input operand in the outputs section, and "%rsi" is in the inputs section, not clobbers.

But as an input it's missing the (var_name) part of the "constraint"(var_name) syntax. So that's a syntax error, as well as a semantic error. That's the immediate source of the error :9:5: error: expected '(' before ')' token. https://godbolt.org/z/97aTdjE8K

As Nate pointed out, you have several other errors, like trying to force the input to pick RSI with "S".

Edited (I missed the part where you fallback on TryGetFormCredentials)

It seems like you need to send the form data as application/x-www-form-urlencoded. See the RFC

Use syscall function code 3 to print doubles (not function code 2 — that's for single float).

Use mov.d to copy one register to another, e.g. into $f12 for sycalls (then no need to load 0.0 into $f0).

(Also, use l.d instead of ldc1.)

The loop: loop isn't a loop (there is no backward branch for it).

As @Peter says, your scaling/offsets are not properly accounting for the size of double, which is 8.  Scaling needs to multiply by 8 (shift by 3, not 2), and offsets need to be multiples of 8.

Your first loop, when its done, should not EXIT the program but rather continue with the next statement (i.e. the printing loop).

For this statement numbers[i+2] = numbers[i+1] + numbers[i]; there are two loads and one store as array references, whereas the assembly code is doing 3 loads and no store.

You use $s5, but never put anything in it.

The comparison of numbers[i+1] < 150 has to be done in (double) floating point, whereas the assembly code is attempting this in integer registers.

Floating point comparison is done using c.eq.d, c.lt.d, or c.le.d.  Like with integer compares, constants need to be in registers before the compare instruction.  150.0 would best come directly from memory (as a double constant) before the loop and remain there for the loop duration (or you can move integer 150 into a floating point register and convert that to double (cvt.w.d)).

Conditional branches on floating point compare conditions use either bc1t or bc1f (depending on the sense you want).

The C-like pseudo code probably doesn't run properly.  The exit condition for the first loop is suspect — it will probably run off the end of the array (depending on its initial data values).

Translating non-working C code into assembly is a recipe for frustration.  Suggest getting it working in C first; run it to make sure it works.

You need to include the using statement, either in the component.razor file, or in _Imports.razor (preferred if you are going to be using JSInterop often):

You are using scalatest version 2.2.6:

The connection string should be configured in the same project where the services connect to the DbContext, so you can leave the appsettings.json as-is.

It is the configuring project (the one that is setting up all the dependencies) that sets the connection to the DB, and the EF migration tool needs the connection to track and apply changes. Any assembly can be used to store migrations, but the EF tool needs to be invoked for a project with an actual connection.

EF Core uses Dependency Injection to configure services for runtime which includes setting the connection string for any DB. The control of how the DB classes interact with their environment is given to the app that is running it, which allows for the same DB code to be used across multiple instances, states and even providers. EF Core uses the current state & provider of the DB where it is deployed to determine changes and scaffolding, so it can only create migrations with a configured instance of a DbContext connected to a DB (usually the development instance).

When a solution is comprised multiple dependent services with a common data model that will need the same migrations, only one of the projects in the solution should be responsible for managing DB state. Whichever project is chosen, it needs to create a DBContext with a valid connection when it starts up for the EF tools to work. ASP.NET Core uses the Microsoft.Extensions.Configuration package and the UseStartup method to make the configuration simple. This can be your existing UI project that would read the connection string from existing settings and pass it to your CustomDbContext at Startup. The EF Tools CLI will use the default profile (the Green run arrow) to get the settings from launchSettings.json and appSettings.json to connect to the DB. The configuration should be in place in each environment you deploy to so that the migrations can be run from the same configuring project and applied as needed.

You can avoid ASP.NET and create a custom startup class in your data package that runs to apply migrations, but this is a lot of extra work for something already in the box. The DbContext class does have an OnConfiguring method that can be used to set the connection. Placing configuration inside of code limits where the software can run, so it should still be set externally.

The DbContext can be referenced from another package:

The DbContext and Models can be defined in a separate 'pure' project, then referenced in the Startup like so:

If you read the assembler code from the top you will see that it reaches .L3, plus it also jumps to it with jne .L3, which is your for loop in C.