| Age | Commit message (Collapse) | Author |
|---|
|
initial RISC-V support
I rebased @alexrp's work (https://github.com/alexrp/mono/commits/riscv) and added stubs so this minimal example works in the interpreter:
```console
$ qemu-riscv64 ./mono/mini/mono-sgen --version
Mono JIT compiler version 5.21.0 (riscv/f4802305009 Wed Nov 7 02:58:20 PST 2018)
Copyright (C) 2002-2014 Novell, Inc, Xamarin Inc and Contributors. www.mono-project.com
TLS: __thread
SIGSEGV: normal
Notifications: epoll
Architecture: riscv64,double-fp
Disabled: none
Misc:
Interpreter: yes
Suspend: preemptive
GC: sgen (concurrent by default)
$ export MONO_PATH=../mono-riscv-bclbuild/b/lib/mono/4.5
$ grep -A 2 test_0_return mono/mini/basic.cs
public static int test_0_return () {
return 0;
}
$ INTERP_FILTER_METHOD=test_0_return qemu-riscv64 ./mono/mini/mono-sgen --interp --regression basic.exe
Test run: image=/home/lewurm/work/mono-riscv/basic.exe
Results: total tests: 1, all pass
Elapsed time: 0.002441 secs (0.002441, 0.000000)
Overall results: tests: 1, 100% pass
```
|
|
TARGET_NET_REFERENCE for individual tools
|
|
|
|
* Move doc comments to profiler.c so they're picked up by exdoc.
* Rewrite mono-api-profiler.html for the new profiler API.
* Clarify some aspects of the doc comments.
|
|
This is unnecessary and messes with code block formatting.
|
|
This doesn't support the full syntax, but it's enough for our needs.
|
|
|
|
This messes with code block formatting.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Avoid globals, use proper data structures instead of strings, and
produce some warnings for documentation errors.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
They were deleted in d1ace1652b2063ea2c416351bd70b32470f55b9b.
|
|
They were deleted in 38cf816b97dff972b996905cd3a8e6ecbfdd2861.
|
|
|
|
The recent sed update in cygwin [1] changed the way sed handles
carriage returns. This meant that every .in file we processed
still contained CR, which doesn't work for .sh files.
Force LF line endings for those files (and also other shell scripts).
[1] https://cygwin.com/ml/cygwin-announce/2017-02/msg00036.html
|
|
|
|
Bare minimum Doxygen configuration with dependency graphs.
|
|
|
|
Introduces a mechanism for non-bridged SCCs which lay between bridged
SCCs in the SCC forest to be reported to the bridge client. In this
version, such non-bridged SCCs are always reported. The result is that
most GCs get a little slower but GCs in which the "double fan" shape
appears (many bridged objects link to one C# object which links to
many bridged objects) become massively faster.
Because before clients were allowed to assume exported SCCs were
always bridged, SGEN_BRIDGE_VERSION has been incremented.
|
|
use full path.
One of csc prerequisites because csc uses -lib as path which is considered after
RuntimeEnvironment.GetRuntimeDirectory which makes -lib useless
|
|
|
|
|
|
|
|
|
|
isolate, fix various processing problems
|
|
|
|
documentation
|
|
Remove ChangeLog files from the repo
|
|
|
|
|
|
|
|
|
|
them as internal
|
|
|
|
They weren't updated in the last 6 years and aren't helpful anymore (e.g. by causing unrelated matches during git grep searches).
|
|
When tracing multi-threaded program execution, it is useful to have a
way of separating which events happen on which thread. The
System.Threading.Thread.Name and Thread.ManagedThreadId properties are
useful proxies for tracking program execution.
However, if program execution spans both managed and embedded mono
native code, there is no existing mechanism to read the Thread.Name or
Thread.ManagedThreadId properties from native code without using
delegates, and delegates may not be usable in all circumstances (e.g.
within a mono_gc_register_bridge_callbacks() callback).
Add the following APIs to the embedding API to permit reading the
Thread.Name and Thread.ManagedThreadId properties:
char *mono_thread_get_name_utf8 (MonoThread *thread);
gint32 mono_thread_get_managed_id (MonoThread *thread);
mono_thread_get_name_utf8() returns the Thread.Name value as a UTF-8
string in newly allocated memory; the caller must g_free() this value.
mono_thread_get_managed_id() returns the Thread.ManagedThreadId value.
|
|
|
|
|
