User forums > Embedded development

Assembler tools for CB

<< < (3/7) > >>

stahta01:

--- Quote from: oBFusCATed on March 08, 2014, 01:35:20 am ---@stahta01: The compiler/sdk in E::B is probably using the old non generic/xml based compilers, so patches taken from there won't work.

--- End quote ---

I agree, I am just looking for the files that needed changed in the SDK/src.
I would guess the same files still need changed; maybe, in different ways.

Edit: Decided adding assembler support is premature; will work on adding $device support to C Compiler instead.
http://forums.codeblocks.org/index.php/topic,19044.msg130362.html#msg130362

Tim S.

BlueHazzard:
Something like this would be nice: http://www.google.de/imgres?sa=X&biw=1366&bih=613&tbm=isch&tbnid=-vSwBoC2DI_HyM%3A&imgrefurl=http%3A%2F%2Fwww.linuxtopia.org%2Fonline_books%2Feclipse_documentation%2Feclipse_c_c%2B%2B_guide%2Ftopic%2Forg.eclipse.cdt.doc.user%2Freference%2Feclipse_c_c%2B%2B_guide_cdt_u_dissassembly_view.htm&docid=5rP1-7dqWQr8KM&imgurl=http%3A%2F%2Fwww.linuxtopia.org%2Fonline_books%2Feclipse_documentation%2Feclipse_c_c%252B%252B_guide%2Ftopic%2Forg.eclipse.cdt.doc.user%2Fimages%2Fview_dissassembly.png&w=491&h=250&ei=-bMcU7zkC4OBywOjh4CIAQ&zoom=1&iact=rc&dur=753&page=1&start=0&ndsp=17&ved=0CGAQrQMwAw a disassembly window which combines source code and assembler code in one window. I have no clue how this is done, but i think this has to come from the debugger or?

oBFusCATed:
This is already supported Debug -> Debug windows -> Disassembly and enable the Mixed mode.

BlueHazzard:

--- Quote from: oBFusCATed on March 09, 2014, 07:51:45 pm ---This is already supported Debug -> Debug windows -> Disassembly and enable the Mixed mode.

--- End quote ---
wow thanks! i somehow missed this!

scarphin:
@obfuscated:
1- That should be enough to achieve syntax highlighting for assembler files imo. I'll try to implement one when I find the time. There is a slightly bigger problem though. Afaik most gcc based embedded compilers use the same file extension for assembler files (.s, .S) so for different gcc based mcu compilers, assembler file extensions becomes the same. I can think of 2 options here, one being the renaming of the assembler files' extension to something specific to the mcu (which I don't know if it will work but quite probably it will) and second choosing a keyword group somehow. Maybe there is a better option.
2- Separating C and C++ options is a good idea as C/C++ files are compiled and thus fit under compiler settings but assembler files are assembled by assembler into object code thus they don't fit under compiler settings. I get the feeling that you don't want to squeeze the main settings tabs to fit an assembler settings tabs there ;) but I think there are other areas of cb quite cluttered too like right-click menu, tabs in Global compiler settings etc... It's your decision in the end but please be aware that pure assembler projects are not that uncommon in embedded world which involve no compilation at all.
3- Assembler files are always assembled into object files for all gcc-based and most other compilers, no doubt with that. What I had in mind was if the C++ function call conventions would be of trouble or not in the linkage stage.

Navigation

[0] Message Index

[#] Next page

[*] Previous page