Displaying 13 results from an estimated 13 matches for "tinycc".
2016 Oct 17
4
unable to compile llvm with gcc 4.7.4
Hi,
The problem is modern c++. I can have a reasonable system boostrape-ed
with (tinycc/alternative C compiler), but only in the gcc world since
a modern c++ compiler is only bootsrape-able from near any C compiler
there. clang and llvm are unable to do it. That why I would need to
get 2 gccs: "any C compiler" -> gcc 4.7.4 -> gcc recent_version ->
llvm.
On Fri, Oct...
2016 Oct 13
2
unable to compile llvm with gcc 4.7.4
...tstrap llvm from a C compiler/runtime, gcc(4.7.4) + gcc(version>=4.8)
> > will have to be setup first.
>
> I want to understand your constraints, as I think this is a unique
> case that I wasn't considering.
It's my custom distro. My goal is to make it boostrap-able with tinycc (or any
little C compiler alternative) as a one-man reasonable job. With the removal of
gcc 4.7 support now official, I would need to have a 3 step bootstrap, adding a
modern gcc (which is guaranted to compile with iso c++98-ish gcc 4.7.4, feature
that clang cannot guaranted anymore).
I'm targ...
2016 Oct 17
4
unable to compile llvm with gcc 4.7.4
...g time before you need a 4
> stage bootstrap :-)
>
>
> On Mon, Oct 17, 2016 at 2:02 PM, Sylvain Bertrand via llvm-dev <
> llvm-dev at lists.llvm.org> wrote:
>
>> Hi,
>>
>> The problem is modern c++. I can have a reasonable system boostrape-ed
>> with (tinycc/alternative C compiler), but only in the gcc world since
>> a modern c++ compiler is only bootsrape-able from near any C compiler
>> there. clang and llvm are unable to do it. That why I would need to
>> get 2 gccs: "any C compiler" -> gcc 4.7.4 -> gcc recent_versi...
2009 Apr 08
2
[LLVMdev] Native Static Compilers Compatible with LLVM
I've tried compiling with tinycc, and assembling with yasm, and fasm even
with intel syntax. I'm just wondering what available compilers and
assemblers there are without trying every one of them.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachm...
2009 Apr 08
0
[LLVMdev] Native Static Compilers Compatible with LLVM
> I've tried compiling with tinycc, and assembling with yasm, and fasm even
> with intel syntax. I'm just wondering what available compilers and
> assemblers there are without trying every one of them.
gas
--
With best regards, Anton Korobeynikov
Faculty of Mathematics and Mechanics, Saint Petersburg State University
2010 Feb 02
2
[LLVMdev] Using LLVM to generate x86 dynamically in memory
...e decided to apply during this code-gen phase.
What we plan to do is invoke this in-memory compiler to generate the x86 instructions, and then ship them at runtime to our new expression evaluation engine that will simply set a function pointer to it and execute.
I heard of a compiler called TinyCC that basically has a library (libtcc) that can be invoked at runtime to generate x86 instructions directly from a C program stored in memory. That's what I would like, but with the aggressive opts provided in the LLVM infrastructure. Thanks so much for your time...
- Shasank...
2010 Feb 03
0
[LLVMdev] Using LLVM to generate x86 dynamically in memory
...t; >
> > > What we plan to do is invoke this in-memory compiler to generate the x86 instructions, and then ship them at runtime to our new expression evaluation engine that will simply set a function pointer to it and execute.
> > >
> > > I heard of a compiler called TinyCC that basically has a library (libtcc) that can be invoked at runtime to generate x86 instructions directly from a C program stored in memory. That's what I would like, but with the aggressive opts provided in the LLVM infrastructure. Thanks so much for your time...
> > >
> > >...
2010 Feb 03
5
[LLVMdev] Using LLVM to generate x86 dynamically in memory
...t your needs are.
>
> > What we plan to do is invoke this in-memory compiler to generate the x86 instructions, and then ship them at runtime to our new expression evaluation engine that will simply set a function pointer to it and execute.
> >
> > I heard of a compiler called TinyCC that basically has a library (libtcc) that can be invoked at runtime to generate x86 instructions directly from a C program stored in memory. That's what I would like, but with the aggressive opts provided in the LLVM infrastructure. Thanks so much for your time...
> >
> > - Shasan...
2010 Feb 02
0
[LLVMdev] Using LLVM to generate x86 dynamically in memory
...and compare to what your needs are.
> What we plan to do is invoke this in-memory compiler to generate the x86 instructions, and then ship them at runtime to our new expression evaluation engine that will simply set a function pointer to it and execute.
>
> I heard of a compiler called TinyCC that basically has a library (libtcc) that can be invoked at runtime to generate x86 instructions directly from a C program stored in memory. That's what I would like, but with the aggressive opts provided in the LLVM infrastructure. Thanks so much for your time...
>
> - Shasank
>...
2015 Jul 20
0
flac on windows 2000
...argv() function from src/share/win_utf8_io/win_utf8_io.c:
if (wgetmainargs(&wargc, &wargv, &wenv, 1, &i) != 0) return 1;
Windows 2000 has slightly older version of msvcrt.dll, and this check
always fails. I found an explanation about it here:
http://lists.gnu.org/archive/html/tinycc-devel/2014-11/msg00005.html
(it's not something that should be fixed, of course)
2002 Sep 30
0
0.98.2 released
...e if I fixed all the nasty bugs now.
v0.98.2 2002-09-30 Timo Sirainen <tss at iki.fi>
+ --with-file-offset-size=32 can now be used to select 32bit file
offsets. Using them should be a bit faster and take a bit less
disk and memory (also needed to compile Dovecot successfully with
TinyCC).
+ maildir_copy_with_hardlinks option works now
+ Check new mail and notify about it to client also after
commands which don't allow full syncing (FETCH, STORE, SEARCH).
Also always send RECENT after EXISTS notify.
+ If we're out of disk space while opening mailbox, notify about i...
2016 Oct 12
2
unable to compile llvm with gcc 4.7.4
On Wed, Oct 12, 2016 at 04:15:44PM +0100, Renato Golin wrote:
> On 12 October 2016 at 14:34, Teresa Johnson via llvm-dev <
> llvm-dev at lists.llvm.org> wrote:
>
> > So I'd first like to understand whether we still want to keep gcc 4.7 as a
> > supported version, or move to 4.8 as was suggested. What is the process for
> > making that change?
> >
>
2018 Sep 19
4
Can i reduce my clang/JIT app in size?
i want to integrate a C source JITer into my application but the
resulting executables are too large
is it possible to reduce the resulting libs/exe some way?
current VS2017/svn build example:
llvm-build\Release\bin\clang-interpreter.exe ~36MB
for now (that can change later)
- i want to jit simple c-code
- no std library or something
- x64 only
- no deep/full architecture optimization needed
-