<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd">
<html lang="en" style='--code-editor-font: var(--default-mono-font, "GitLab Mono"), JetBrains Mono, Menlo, DejaVu Sans Mono, Liberation Mono, Consolas, Ubuntu Mono, Courier New, andale mono, lucida console, monospace;'>
<head>
<meta content="text/html; charset=US-ASCII" http-equiv="Content-Type">
<title>
GitLab
</title>
<style data-premailer="ignore" type="text/css">
a { color: #1068bf; }
</style>
<style>img {
max-width: 100%; height: auto;
}
body {
font-size: .875rem;
}
body {
-webkit-text-shadow: rgba(255,255,255,.01) 0 0 1px;
}
body {
font-family: var(--default-regular-font, "GitLab Sans"),-apple-system,BlinkMacSystemFont,"Segoe UI",Roboto,"Noto Sans",Ubuntu,Cantarell,"Helvetica Neue",sans-serif,"Apple Color Emoji","Segoe UI Emoji","Segoe UI Symbol","Noto Color Emoji"; font-size: inherit;
}
</style>
</head>
<body style='font-size: inherit; -webkit-text-shadow: rgba(255,255,255,.01) 0 0 1px; font-family: var(--default-regular-font, "GitLab Sans"),-apple-system,BlinkMacSystemFont,"Segoe UI",Roboto,"Noto Sans",Ubuntu,Cantarell,"Helvetica Neue",sans-serif,"Apple Color Emoji","Segoe UI Emoji","Segoe UI Symbol","Noto Color Emoji";'>
<div class="content">
<p style="color: #777777;">
<a href="https://gitlab.rtems.org/the.m3chanic">Suraj Kumar</a>
<a href="https://gitlab.rtems.org/groups/rtems/-/epics/1#note_108823">commented</a>:
</p>
<div class="md" style="color: #333238; word-wrap: break-word;">
<p dir="auto" style="color: #333238; margin: 0 0 16px;" align="initial">I am posting all my updates so far as comments here as per gedare's suggestion</p>
<p dir="auto" style="color: #333238; margin: 0 0 16px;" align="initial">Week 1:</p>
<div class="gl-relative markdown-code-block js-markdown-code">
<pre class="code highlight js-syntax-highlight language-plaintext" v-pre="true" style='display: block; font-size: 14px; color: #333238; line-height: 1.6em; overflow-x: auto; border-radius: 4px; position: relative; font-family: var(--default-mono-font, "GitLab Mono"),"JetBrains Mono","Menlo","DejaVu Sans Mono","Liberation Mono","Consolas","Ubuntu Mono","Courier New","andale mono","lucida console",monospace; word-break: break-all; word-wrap: break-word; background-color: #fbfafd; margin: 0 0 16px; padding: 12px; border: 1px solid #dcdcde;'><code style='font-size: inherit; color: inherit; word-wrap: normal; word-break: keep-all; background-color: inherit; border-radius: 4px; white-space: pre; margin-top: 0; font-family: var(--default-mono-font, "GitLab Mono"),"JetBrains Mono","Menlo","DejaVu Sans Mono","Liberation Mono","Consolas","Ubuntu Mono","Courier New","andale mono","lucida console",monospace; vertical-align: bottom; overflow-wrap: normal; padding: unset;'><span id="LC1" class="line" lang="plaintext" style="margin-top: 0;">Planned:</span>
<span id="LC2" class="line" lang="plaintext">[+] Set up blog website for writing weekly blogs for GSoC</span>
<span id="LC3" class="line" lang="plaintext">[+] Learn about basic kernel structures (mainly semaphores & task control blocks)</span>
<span id="LC4" class="line" lang="plaintext">[+] Set up a debugging environment for testing out C++ applications via GDB </span>
<span id="LC5" class="line" lang="plaintext">[+] Go through my host GDB installation vs RTEMS' GDB installation to identify differences, then look at existing pretty printing scripts (including the ones Chris had linked for me when I was writing my proposal)</span>
<span id="LC6" class="line" lang="plaintext"></span>
<span id="LC7" class="line" lang="plaintext">Done: </span>
<span id="LC8" class="line" lang="plaintext">[+] Set up blog successfully ✅</span>
<span id="LC9" class="line" lang="plaintext">[+] Learned about semaphores, I'm reading from a book so I also ended up delving deeper into other OS related things apart from just structures, to get a better general idea overall </span>
<span id="LC10" class="line" lang="plaintext">[+] Set up a debugging environment, and tested GDB on various C++ programs implementing different STL objects, across different BSPs on various architectures (namely arm/xilinx_zynq_a9_qemu, x86_64/amd64, sparc/leon3) ✅</span>
<span id="LC11" class="line" lang="plaintext">[+] Went through the basic files present in both, kind of got lost in trying to understand the context of various files in there - spent some time on that. Also looked at existing pretty printing implementations and tried to get a side-by-side view on C++ STL objects that I write vs the implementation and how they're handled by the pretty-printer. </span>
<span id="LC12" class="line" lang="plaintext"></span>
<span id="LC13" class="line" lang="plaintext"></span>
<span id="LC14" class="line" lang="plaintext">Blockers: </span>
<span id="LC15" class="line" lang="plaintext">[-] Not too many, except I was travelling from home to college midway so lost about 1.5 days on that </span></code></pre>
<copy-code></copy-code>
</div>
<p dir="auto" style="color: #333238; margin: 0 0 16px;" align="initial">Week 2:</p>
<div class="gl-relative markdown-code-block js-markdown-code">
<pre class="code highlight js-syntax-highlight language-plaintext" v-pre="true" style='display: block; font-size: 14px; color: #333238; line-height: 1.6em; overflow-x: auto; border-radius: 4px; position: relative; font-family: var(--default-mono-font, "GitLab Mono"),"JetBrains Mono","Menlo","DejaVu Sans Mono","Liberation Mono","Consolas","Ubuntu Mono","Courier New","andale mono","lucida console",monospace; word-break: break-all; word-wrap: break-word; background-color: #fbfafd; margin: 0 0 16px; padding: 12px; border: 1px solid #dcdcde;'><code style='font-size: inherit; color: inherit; word-wrap: normal; word-break: keep-all; background-color: inherit; border-radius: 4px; white-space: pre; margin-top: 0; font-family: var(--default-mono-font, "GitLab Mono"),"JetBrains Mono","Menlo","DejaVu Sans Mono","Liberation Mono","Consolas","Ubuntu Mono","Courier New","andale mono","lucida console",monospace; vertical-align: bottom; overflow-wrap: normal; padding: unset;'><span id="LC1" class="line" lang="plaintext" style="margin-top: 0;">Planned: </span>
<span id="LC2" class="line" lang="plaintext">- Design initialisation hook to run GDB commands for specific installation prefixes on GDB, which run every time GDB is loaded</span>
<span id="LC3" class="line" lang="plaintext">- Continue learning about Task Control Blocks</span>
<span id="LC4" class="line" lang="plaintext"></span>
<span id="LC5" class="line" lang="plaintext">Done: </span>
<span id="LC6" class="line" lang="plaintext">- Have good progress on various ways in which I can design the initialisation hook (narrowed it down to 3 methods - 2 sub-par and 1 ideal) [`~/.gdbinit`, `-x init.gdb`, `auto-load` directory]</span>
<span id="LC7" class="line" lang="plaintext">- Learned more about Task Control Blocks and Process Environment Blocks and how PEB's work (sources: https://pages.cs.wisc.edu/~remzi/OSTEP/, https://ia801902.us.archive.org/28/items/operating-system-concepts-10th/operating-system-concepts-10th.pdf)</span>
<span id="LC8" class="line" lang="plaintext"></span>
<span id="LC9" class="line" lang="plaintext">Blockers: </span>
<span id="LC10" class="line" lang="plaintext">- Got sick, so couldn't work for about a day and a half in between</span>
<span id="LC11" class="line" lang="plaintext"></span>
<span id="LC12" class="line" lang="plaintext">Planned for next week: </span>
<span id="LC13" class="line" lang="plaintext">- Finish designing the initialisation hook on GDB</span>
<span id="LC14" class="line" lang="plaintext">- Look into setting up a kernel debugging environment on RTEMS</span></code></pre>
<copy-code></copy-code>
</div>
<p dir="auto" style="color: #333238; margin: 0 0 16px;" align="initial">Week 3:</p>
<div class="gl-relative markdown-code-block js-markdown-code">
<pre class="code highlight js-syntax-highlight language-plaintext" v-pre="true" style='display: block; font-size: 14px; color: #333238; line-height: 1.6em; overflow-x: auto; border-radius: 4px; position: relative; font-family: var(--default-mono-font, "GitLab Mono"),"JetBrains Mono","Menlo","DejaVu Sans Mono","Liberation Mono","Consolas","Ubuntu Mono","Courier New","andale mono","lucida console",monospace; word-break: break-all; word-wrap: break-word; background-color: #fbfafd; margin: 0 0 16px; padding: 12px; border: 1px solid #dcdcde;'><code style='font-size: inherit; color: inherit; word-wrap: normal; word-break: keep-all; background-color: inherit; border-radius: 4px; white-space: pre; margin-top: 0; font-family: var(--default-mono-font, "GitLab Mono"),"JetBrains Mono","Menlo","DejaVu Sans Mono","Liberation Mono","Consolas","Ubuntu Mono","Courier New","andale mono","lucida console",monospace; vertical-align: bottom; overflow-wrap: normal; padding: unset;'><span id="LC1" class="line" lang="plaintext" style="margin-top: 0;">Planned: </span>
<span id="LC2" class="line" lang="plaintext">- Get auto-loading + pretty-printing to work </span>
<span id="LC3" class="line" lang="plaintext">- Look into setting up kernel debugging environment (i sort of pushed this back a bit to focus more on the init-hook, will work on it in the upcoming weeks)</span>
<span id="LC4" class="line" lang="plaintext"></span>
<span id="LC5" class="line" lang="plaintext">Done:</span>
<span id="LC6" class="line" lang="plaintext">- Finalised on .debug_gdb_scripts approach to adding initialisation hook, and got auto-loading + pretty-printing to work perfectly, working on different approaches to handle exception it causes (should be easy)</span>
<span id="LC7" class="line" lang="plaintext">- Looking into adding config flag when building GDB from source to add system-wide gdbinit directory </span>
<span id="LC8" class="line" lang="plaintext">- Modifying linkercmd script to add custom section to script without "section outside of ELF segment warning"</span>
<span id="LC9" class="line" lang="plaintext"></span>
<span id="LC10" class="line" lang="plaintext">Blockers:</span>
<span id="LC11" class="line" lang="plaintext">- </span>
<span id="LC12" class="line" lang="plaintext"></span>
<span id="LC13" class="line" lang="plaintext">Planned for the coming week:</span>
<span id="LC14" class="line" lang="plaintext">- Modify linkercmd script to add section to ELF when building app for one BSP, then implement the same to every BSP</span>
<span id="LC15" class="line" lang="plaintext">- Figure out way to keep track of path to said initialisation script </span>
<span id="LC16" class="line" lang="plaintext">- (possibly) explore option of modifying config options when building GDB to test "{prefix}/usr/share/gdb/system-gdbinit" as the system-wide init directory </span></code></pre>
<copy-code></copy-code>
</div>
<p dir="auto" style="color: #333238; margin: 0 0 16px;" align="initial">Week 4:</p>
<div class="gl-relative markdown-code-block js-markdown-code">
<pre class="code highlight js-syntax-highlight language-plaintext" v-pre="true" style='display: block; font-size: 14px; color: #333238; line-height: 1.6em; overflow-x: auto; border-radius: 4px; position: relative; font-family: var(--default-mono-font, "GitLab Mono"),"JetBrains Mono","Menlo","DejaVu Sans Mono","Liberation Mono","Consolas","Ubuntu Mono","Courier New","andale mono","lucida console",monospace; word-break: break-all; word-wrap: break-word; background-color: #fbfafd; margin: 0 0 16px; padding: 12px; border: 1px solid #dcdcde;'><code style='font-size: inherit; color: inherit; word-wrap: normal; word-break: keep-all; background-color: inherit; border-radius: 4px; white-space: pre; margin-top: 0; font-family: var(--default-mono-font, "GitLab Mono"),"JetBrains Mono","Menlo","DejaVu Sans Mono","Liberation Mono","Consolas","Ubuntu Mono","Courier New","andale mono","lucida console",monospace; vertical-align: bottom; overflow-wrap: normal; padding: unset;'><span id="LC1" class="line" lang="plaintext" style="margin-top: 0;">Planned: </span>
<span id="LC2" class="line" lang="plaintext">- Modify linkercmd script to add section to ELF when building app for one BSP, then implement the same to every BSP</span>
<span id="LC3" class="line" lang="plaintext">- Figure out way to keep track of path to said initialisation script </span>
<span id="LC4" class="line" lang="plaintext">- Explore option of modifying config options when building GDB to test "{prefix}/usr/share/gdb/system-gdbinit" as the system-wide init directory</span>
<span id="LC5" class="line" lang="plaintext">- Get at least auto-loading to work along with linker modifications</span>
<span id="LC6" class="line" lang="plaintext"></span>
<span id="LC7" class="line" lang="plaintext"></span>
<span id="LC8" class="line" lang="plaintext">Done: </span>
<span id="LC9" class="line" lang="plaintext">- Successfully did linkercmd.base modifications and got pretty-printing to work, although, hit roadblock when finding ways to keep track of path to pretty-printing script</span>
<span id="LC10" class="line" lang="plaintext">- Got config option modification to work, but ruled it out for non-optimal design </span>
<span id="LC11" class="line" lang="plaintext">- Went back and forth with GDB devs regarding possible solutions for issue, then discovered that there is no solid one at the moment </span>
<span id="LC12" class="line" lang="plaintext">- Discovered new way of loading script (embedding script text inside section). Tested it, and it works well without any need of maintaining paths. Currently working with mentors to try and finalise on one approach </span>
<span id="LC13" class="line" lang="plaintext"></span>
<span id="LC14" class="line" lang="plaintext">Blockers: </span>
<span id="LC15" class="line" lang="plaintext">- Very little/no documentation for the problem i am trying to fix, so finding ways that work + will be sustainable on RTEMS is quite challenging</span>
<span id="LC16" class="line" lang="plaintext"></span>
<span id="LC17" class="line" lang="plaintext">Planned for next week:</span>
<span id="LC18" class="line" lang="plaintext">- Work with mentors & hopefully finalise on approach. Currently i'm not too sure what I can plan ahead to make my work optimal </span></code></pre>
<copy-code></copy-code>
</div>
<p dir="auto" style="color: #333238; margin: 0 0 16px;" align="initial">Week 5:</p>
<div class="gl-relative markdown-code-block js-markdown-code">
<pre class="code highlight js-syntax-highlight language-plaintext" v-pre="true" style='display: block; font-size: 14px; color: #333238; line-height: 1.6em; overflow-x: auto; border-radius: 4px; position: relative; font-family: var(--default-mono-font, "GitLab Mono"),"JetBrains Mono","Menlo","DejaVu Sans Mono","Liberation Mono","Consolas","Ubuntu Mono","Courier New","andale mono","lucida console",monospace; word-break: break-all; word-wrap: break-word; background-color: #fbfafd; margin: 0 0 16px; padding: 12px; border: 1px solid #dcdcde;'><code style='font-size: inherit; color: inherit; word-wrap: normal; word-break: keep-all; background-color: inherit; border-radius: 4px; white-space: pre; margin-top: 0; font-family: var(--default-mono-font, "GitLab Mono"),"JetBrains Mono","Menlo","DejaVu Sans Mono","Liberation Mono","Consolas","Ubuntu Mono","Courier New","andale mono","lucida console",monospace; vertical-align: bottom; overflow-wrap: normal; padding: unset;'><span id="LC1" class="line" lang="plaintext" style="margin-top: 0;">Planned: </span>
<span id="LC2" class="line" lang="plaintext">[Was a bit shaky at first, i.e, was not sure what to do], nevertheless</span>
<span id="LC3" class="line" lang="plaintext">- Go through implementations of workarounds to the current problem (those by Rust and AdaCore)</span>
<span id="LC4" class="line" lang="plaintext">- Understand the dependencies of both implementations, and weigh their pros and cons </span>
<span id="LC5" class="line" lang="plaintext">- Work together with mentors on the current approaches I have, and get on the same page as them</span>
<span id="LC6" class="line" lang="plaintext">- Discuss with Rust & AdaCore users on their workarounds to the current problems, to get a better insight</span>
<span id="LC7" class="line" lang="plaintext"></span>
<span id="LC8" class="line" lang="plaintext">Done: </span>
<span id="LC9" class="line" lang="plaintext">- Researched about Rust's wrapper, and found most of its pros and cons (from [here](https://github.com/rust-lang/rust/commits/master/src/etc/rust-gdb), we can see that it was modified only once in the last 10 years due to an arg conflict, rest were quality-of-life improvements)</span>
<span id="LC10" class="line" lang="plaintext">- Decided not to go ahead with Rust's solution due to lack of benefits and conflicting design choices</span>
<span id="LC11" class="line" lang="plaintext">- Worked with mentors and finalised an approach (adding Python script to .debug_gdb_scripts section)</span>
<span id="LC12" class="line" lang="plaintext">- Looked into using linker command scripts to modify section content at compile/linking time without modifying script source (reading from here: https://users.informatik.haw-hamburg.de/~krabat/FH-Labor/gnupro/5_GNUPro_Utilities/c_Using_LD/ldLinker_scripts.html#Output_section_data)</span>
<span id="LC13" class="line" lang="plaintext"></span>
<span id="LC14" class="line" lang="plaintext">Blockers: </span>
<span id="LC15" class="line" lang="plaintext">- Lack of resources/discussions from previous people struggling with the same problem </span>
<span id="LC16" class="line" lang="plaintext"></span>
<span id="LC17" class="line" lang="plaintext"></span>
<span id="LC18" class="line" lang="plaintext">Planned: </span>
<span id="LC19" class="line" lang="plaintext">- Find out way to reference pre-installed GCC files from embedded script without external dependencies</span>
<span id="LC20" class="line" lang="plaintext">- Find out reliable method to modify output section content through linker command files (or something under the hood, not involving the user) </span></code></pre>
<copy-code></copy-code>
</div>
<p dir="auto" style="color: #333238; margin: 0 0 16px;" align="initial">Week 6:</p>
<div class="gl-relative markdown-code-block js-markdown-code">
<pre class="code highlight js-syntax-highlight language-plaintext" v-pre="true" style='display: block; font-size: 14px; color: #333238; line-height: 1.6em; overflow-x: auto; border-radius: 4px; position: relative; font-family: var(--default-mono-font, "GitLab Mono"),"JetBrains Mono","Menlo","DejaVu Sans Mono","Liberation Mono","Consolas","Ubuntu Mono","Courier New","andale mono","lucida console",monospace; word-break: break-all; word-wrap: break-word; background-color: #fbfafd; margin: 0 0 16px; padding: 12px; border: 1px solid #dcdcde;'><code style='font-size: inherit; color: inherit; word-wrap: normal; word-break: keep-all; background-color: inherit; border-radius: 4px; white-space: pre; margin-top: 0; font-family: var(--default-mono-font, "GitLab Mono"),"JetBrains Mono","Menlo","DejaVu Sans Mono","Liberation Mono","Consolas","Ubuntu Mono","Courier New","andale mono","lucida console",monospace; vertical-align: bottom; overflow-wrap: normal; padding: unset;'><span id="LC1" class="line" lang="plaintext" style="margin-top: 0;">[Update is only for work since this Monday, and Wednesday-Thursday 2 weeks back]</span>
<span id="LC2" class="line" lang="plaintext">Planned: </span>
<span id="LC3" class="line" lang="plaintext">1. Write stdcxx.py to register pretty-printers after finding path to GCC</span>
<span id="LC4" class="line" lang="plaintext">2. Modify linkcmds to add custom section to ELF every time when compiling</span>
<span id="LC5" class="line" lang="plaintext">2. Start work on RSB to figure out GCC version dynamically (at build time)</span>
<span id="LC6" class="line" lang="plaintext"></span>
<span id="LC7" class="line" lang="plaintext">Done: </span>
<span id="LC8" class="line" lang="plaintext">1. Wrote stdcxx.py</span>
<span id="LC9" class="line" lang="plaintext">2. Modified linkcmds.base </span>
<span id="LC10" class="line" lang="plaintext">3. Working on RSB detailing to find GCC version</span>
<span id="LC11" class="line" lang="plaintext">4. Drafting MRs for adding stdcxx.py as well as linkcmds.base modifications for ARM, currently building from source and testing </span>
<span id="LC12" class="line" lang="plaintext"></span>
<span id="LC13" class="line" lang="plaintext">Blockers: </span>
<span id="LC14" class="line" lang="plaintext">None </span>
<span id="LC15" class="line" lang="plaintext"></span>
<span id="LC16" class="line" lang="plaintext">Planned for coming week:</span>
<span id="LC17" class="line" lang="plaintext">1. Merge both MRs </span>
<span id="LC18" class="line" lang="plaintext">2. Finalise RSB detailings to identify GCC version(s)</span>
<span id="LC19" class="line" lang="plaintext">3. Test this feature on various BSPS/architectures to identify which platforms it works on and how I can identify it </span></code></pre>
<copy-code></copy-code>
</div>
<p dir="auto" style="color: #333238; margin: 0 0 16px;" align="initial">Week 7:</p>
<div class="gl-relative markdown-code-block js-markdown-code" style="margin-bottom: 0;">
<pre class="code highlight js-syntax-highlight language-plaintext" v-pre="true" style='display: block; font-size: 14px; color: #333238; line-height: 1.6em; overflow-x: auto; border-radius: 4px; position: relative; font-family: var(--default-mono-font, "GitLab Mono"),"JetBrains Mono","Menlo","DejaVu Sans Mono","Liberation Mono","Consolas","Ubuntu Mono","Courier New","andale mono","lucida console",monospace; word-break: break-all; word-wrap: break-word; background-color: #fbfafd; margin: 0 0 16px; padding: 12px; border: 1px solid #dcdcde;'><code style='font-size: inherit; color: inherit; word-wrap: normal; word-break: keep-all; background-color: inherit; border-radius: 4px; white-space: pre; margin-top: 0; font-family: var(--default-mono-font, "GitLab Mono"),"JetBrains Mono","Menlo","DejaVu Sans Mono","Liberation Mono","Consolas","Ubuntu Mono","Courier New","andale mono","lucida console",monospace; vertical-align: bottom; overflow-wrap: normal; padding: unset;'><span id="LC1" class="line" lang="plaintext" style="margin-top: 0;">Planned:</span>
<span id="LC2" class="line" lang="plaintext">1. Merge both MRs [this got corrected to just one MR, which is a WIP currently]</span>
<span id="LC3" class="line" lang="plaintext">2. Finalise RSB detailings to identify GCC version(s)</span>
<span id="LC4" class="line" lang="plaintext">3. Test this feature on various BSPS/architectures to identify which platforms it works on and how I can identify it </span>
<span id="LC5" class="line" lang="plaintext"></span>
<span id="LC6" class="line" lang="plaintext"></span>
<span id="LC7" class="line" lang="plaintext">Done: </span>
<span id="LC8" class="line" lang="plaintext">1. Tested feature across following architectures/BSPs:</span>
<span id="LC9" class="line" lang="plaintext"> a. aarch64/raspberrypi4b - 64-bit LSB</span>
<span id="LC10" class="line" lang="plaintext"> b. bfin/eZKit533 - 32-bit LSB</span>
<span id="LC11" class="line" lang="plaintext"> c. powerpc/qemuppc - 32-bit MSB</span>
<span id="LC12" class="line" lang="plaintext"> d. sparc/leon3 - 32-bit MSB</span>
<span id="LC13" class="line" lang="plaintext"> e. sparc64/niagara - 64-bit MSB (relaxed memory ordering)</span>
<span id="LC14" class="line" lang="plaintext"> f. x86_64/amd64 - 64-bit LSB</span>
<span id="LC15" class="line" lang="plaintext"> g. i386/pc386 - 32-bit LSB </span>
<span id="LC16" class="line" lang="plaintext"> h. riscv/mpfs64imafdc - 64-bit LSB</span>
<span id="LC17" class="line" lang="plaintext"> i. x86_64/amd64 - 64-bit LSB</span>
<span id="LC18" class="line" lang="plaintext"> j. arm/xilinx_zynq_a9_qemu - 32-bit LSB</span>
<span id="LC19" class="line" lang="plaintext"> k. sh/simsh4 - 32-bit LSB</span>
<span id="LC20" class="line" lang="plaintext"> l. or1k/generic_or1k - 32-bit MSB</span>
<span id="LC21" class="line" lang="plaintext"> m. v850/v850e2v3sim - 32-bit LSB</span>
<span id="LC22" class="line" lang="plaintext"> n. nios2/nios2_iss - 32-bit LSB</span>
<span id="LC23" class="line" lang="plaintext"> o. moxie/moxiesim - 32-bit MSB</span>
<span id="LC24" class="line" lang="plaintext"></span>
<span id="LC25" class="line" lang="plaintext">2. Identified parts of RSB scripts to work on to retrieve GCC Version info, and came up with a few ideas to incorporate into script</span>
<span id="LC26" class="line" lang="plaintext">3. Started making final commits to the MR to modify linker scripts for every architecture (https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/98), remaining linker scripts are under-way, following which commit for modification to cpukit/sapi/src/exinit.c is ready but waiting for linker mods first</span>
<span id="LC27" class="line" lang="plaintext"></span>
<span id="LC28" class="line" lang="plaintext">Blockers: </span>
<span id="LC29" class="line" lang="plaintext">Spent almost a day's worth of time building/fixing LLVM & Python version update issues</span>
<span id="LC30" class="line" lang="plaintext"></span>
<span id="LC31" class="line" lang="plaintext">Planned for coming week: </span>
<span id="LC32" class="line" lang="plaintext">1. MR with changes to RSB script (gcc-common-1.cfg)</span>
<span id="LC33" class="line" lang="plaintext">2. Merge MR which will add section to ELFs</span>
<span id="LC34" class="line" lang="plaintext">3. Modify documentation mentioning to add line (`set auto-load safe-path /`) to ~/.gdbinit. [I am not yet sure where this addition would come, but think it would be necessary because users will try and load their executable into GDB and get an error about the inlined script not being inside auto-load safe-path]</span></code></pre>
<copy-code></copy-code>
</div>
</div>
</div>
<div class="footer" style="margin-top: 10px;">
<p style="font-size: small; color: #737278;">
—
<br>
<a href="https://gitlab.rtems.org/groups/rtems/-/epics/1#note_108823">View it on GitLab</a>.
<br>
You're receiving this email because of your account on <a target="_blank" rel="noopener noreferrer" href="https://gitlab.rtems.org">gitlab.rtems.org</a>. <a href="https://gitlab.rtems.org/-/sent_notifications/70a51d36bbd6960b73d5b0d83cfb7276/unsubscribe" target="_blank" rel="noopener noreferrer">Unsubscribe</a> from this thread · <a href="https://gitlab.rtems.org/-/profile/notifications" target="_blank" rel="noopener noreferrer" class="mng-notif-link">Manage all notifications</a> · <a href="https://gitlab.rtems.org/help" target="_blank" rel="noopener noreferrer" class="help-link">Help</a>
<script type="application/ld+json">{"@context":"http://schema.org","@type":"EmailMessage","action":{"@type":"ViewAction","name":"View Epic","url":"https://gitlab.rtems.org/groups/rtems/-/epics/1#note_108823"}}</script>
</p>
</div>
</body>
</html>