Minimal linker script for cortex M3 and M4 using gcc for c language applications

ation about the entries marked with ???-> Thanks a lot! Sergio MEMORY { flash(rx) : ORIGIN = 0, LENGTH = 512K ram(wx) : ORIGIN = 0x2200, LENGTH = 64K-0x200 } SECTIONS { . = 0; .text : { KEEP(*(.isr_vector)) *(.text)

Extension for a throw-like C++ qualifier

every exception not enclosed into a try { } catch { } block may be thrown, the check can be done at runtime. The overall idea is, of course, to give information to the caller about the exceptions it must handle. I think that this extension would worth the while. Any ideas? Cheers, Sergio

Re: Extension for a throw-like C++ qualifier

oh-so-cleverly named _throw) and allow such an extension for the language which something like -fallow_throw. Cheers, Sergio On 3/30/07, Mike Stump <[EMAIL PROTECTED]> wrote: On Mar 30, 2007, at 11:05 AM, Sergio Giro wrote: > int TheClass::exceptMethod() _throw TheException { >

Re: Extension for a throw-like C++ qualifier

, if you don't allow template exceptions to be used in the _throw qualifier. I think that the hard step is to put it into gcc. I will be grateful for any advise on how to start looking add in order to implement this new feature. Cheers, Sergio On 3/30/07, Mike Stump <[EMAIL P

Re: Extension for a throw-like C++ qualifier

is is not useful... If you consider this analysis to be useful, I will be grateful for any ideas concerning where and how to start looking in order to implement the analysis. Cheers, Sergio On 4/2/07, Mike Stump <[EMAIL PROTECTED]> wrote: Ah, yeah, that I suspect woul

Inclusion in an official release of a new throw-like qualifier

release, I prefer to contribute to eDoc++ (edoc.sourceforge.net), an (almost) existing tool which performs the test "outside" gcc. All the best, Sergio

Re: Inclusion in an official release of a new throw-like qualifier

d c, but, in addition to the exceptions, you may get a nasty call to unexpected()... The idea is that if you can write int main() _throw () { yourCode(); } and your code compile, you will not have unexpected exceptions thrown during the execution of your program. Moreover, you have better control of the exceptions that can be thrown in every point of the execution... All the best, Sergio

Re: Inclusion in an official release of a new throw-like qualifier

g the prototypes... I agree with Jason that an extension which implies rewriting everything is not very likely to be included, but it is not case. So, what do you think now? Cheers, Sergio

Re: Inclusion in an official release of a new throw-like qualifier

Mike Stump wrote: Let me try again. The standard way to add a new qualifier in g++, is to add it in an attribute, please do that. OK, I agree. Let's say that a method will be declared as int method() throw(std::exception) __attribute__((static_exc_check)); (this is intended to have the same mea

Re: Inclusion in an official release of a new throw-like qualifier

one provided by programmer in the prototypes. Maybe someone later can save the programer to write unuseful code. It seems to me that fully accomplishing what you are talking about needs an algorithm for the halting problem, and I plan to have such an algorithm not until 2009 :D . All the best, Sergio

Is the GCC optimazer too smart?

that the compiler enforces the constantness of the variable, even tought it states in the warning that the const qualifier has been discarded? Best Regards Sergio -- preferisco ammazzare il tempo, preferisco sparare cazzate, preferisco fare esplodere una moda, preferisco morire d'amore. (Caparezza)

porting GCC to a micro with a very limited addressing mode --- what to write in LEGITIMATE_ADDRESS, LEGITIMIZE_ADDRESS and micro.md ?!

*/. What should I do? How the addressing mode(s) are managed in the md files and the LEGITxxx_ADDRESS() macros ? The GCC manual is not very clear on this... Is there any other architecture/documentation I should look at ? Thanks, Sergio

Re: porting GCC to a micro with a very limited addressing mode --- what to write in LEGITIMATE_ADDRESS, LEGITIMIZE_ADDRESS and micro.md ?!

Gabriel Paubert wrote: > On Mon, Jan 25, 2010 at 01:34:09PM +0100, Sergio Ruocco wrote: >> Hi everyone, >> >> I am porting GCC to a custom 16-bit microcontroller with very limited >> addressing modes. Basically, it can only load/store using a (general >> purpose)

Re: porting GCC to a micro with a very limited addressing mode --- what to write in LEGITIMATE_ADDRESS, LEGITIMIZE_ADDRESS and micro.md ?!

till fails to generate the assembly code to do the arithmetic computation of the baseReg+offset-->tempReg, and then use (tempReg) as address. Note that with the current MD GCC is able to generate simple sums like R1 = R2 + R3 and R1 = R2 + IMM, thus the basic math to compute an address is there.

Re: porting GCC to a micro with a very limited addressing mode --- success with LEGITIMATE / LEGITIMIZE_ADDRESS, stuck with ICE !

Michael Hope wrote: > Hi Sergio. Any luck so far? Micheal, thanks for your inquiry. I made some progress, in fact. I got the GO_IF_LEGITIMATE_ADDRESS() macro to detect correctly REG+IMM addresses, and then the LEGITIMIZE_ADDRESS() macro to force them to be pre-computed in a register. Howe

Re: porting GCC to a micro with a very limited addressing mode --- enforcing a 'register indirect memory operand' through a constraint in md

custom constraint in the MD (details below). What do you think of this approach? Sergio (from the patch to the MD) - ;; Constraints

Re: porting GCC to a micro with a very limited addressing mode --- enforcing a 'register indirect memory operand' through a constraint in md

ort so far! Sergio (*) void spim_prologue(void) { int i,j; emit_move_insn(gen_rtx_MEM(HImode,plus_constant(stack_pointer_rtx,0)),return_addr_rtx); emit_move_insn(gen_rtx_MEM(HImode,plus_constant(stack_pointer_rtx,-2)),stack_pointer_rtx); emit_move_insn(gen_rtx_MEM(HImode,plu

Re: GCC porting tutorials

Hi Radu, Check both the GCC Wiki and the work done at IIT Bombay: http://www.cse.iitb.ac.in/grc/reach.html Activities->Workshops They developed some tutorials on porting GCC and writing new backends, such as: http://www.cse.iitb.ac.in/grc/gcc-workshop-09/ http://www.cse.iitb.ac.in/~uday/gcc-mini-

Trouble with MDs: "const" RTL object stops recognition of RTL expressions by insn patterns

etic instructions. */ DEF_RTL_EXPR(CONST, "const", "e", RTX_CONST_OBJ) So, what is my port missing to make it compile such RTL expressions? I feel that it must be something really trivial which I am overlooking.. Thanks for your help, Sergio

Re: [AD] UltraGDB, an alternative tool to debug GCC, GDB, LLDB, etc. on Windows and Linux

for demos. Hello Chiheng, I tried to find the source code of this package, but I could not find it. Do you have a URL or something you can provide? Thank you, -- Sergio GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36 Please send encrypted e-mail if possible http://sergiodj.net/

Re: [AD] UltraGDB, an alternative tool to debug GCC, GDB, LLDB, etc. on Windows and Linux

y are Free Software as well, of course), but it looks to me that Standalone Debugger offers a better user experience than UltraGDB. Thank you, -- Sergio GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36 Please send encrypted e-mail if possible http://sergiodj.net/

Pointer to the current function

Hello: I wonder what do you think about a patch to implement getting a pointer to the current function. Is it a "no, under no circumstances"? Or it is a "maybe, show us the code"? I'll explain better what I mean: currently there is the statement __func__ that returns a string with the name o

Re: Updated Sourceware infrastructure plans

On Wednesday, May 01 2024, Mark Wielaard wrote: [...] > But the part that interests me most is the self-registration part that > Sergio setup. I believe we will need that for whatever system we end > up with to make it as easy to contribute as it is with email. > https://blog.sergio