profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/sajattack/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
Paul Sajna sajattack https://paulsajna.com I program my home computer / Beam myself into the future

overdrivenpotato/rust-psp 312

Rust on PSP. Panic and allocation support. Access PSP system libraries.

redox-os/book 96

Mirror of https://gitlab.redox-os.org/redox-os/book

riscv-rust/gd32vf103xx-hal 34

HAL for GD32VF103 microcontrollers

riscv-rust/gd32vf103-pac 25

Peripheral access crate for GD32VF103

PSP-Archive/dosbox_psp 9

DOSBox with PSP patches applied. Originally ported to the PSP by crazyc.

BenBergman/lis3dh-rs 2

Rust library for LIS3DH accelerometer based on embedded-hal

pspdev/gdb 2

The GNU debugger for PSP

jessebraham/atsamd 1

Target atsamd microcontrollers using Rust

luigiplr/emoji-client 1

Hack Victoria 2016 project

issue openedmamedev/mame

TMS34010: Incorrect disassembly

https://github.com/mamedev/mame/blob/2413a02285c14daf354c24dc3ac2baab2d364350/src/devices/cpu/tms34010/34010dsm.cpp#L567

These should both be MOVB, not one MOVE and one MOVB, see the TMS34010 Users Guide movb

created time in 40 minutes

pull request commentatsamd-rs/atsamd

Minor `gpio` updates

I gave it a kick here https://github.com/atsamd-rs/atsamd/actions/runs/1075234166

bradleyharden

comment created time in 3 days

pull request commentatsamd-rs/atsamd

Embedded graphics 7.0 update

Sure.

jacobrosenthal

comment created time in 7 days

create barnchpspdev/binutils-gdb

branch : binutils-2_23_2-PSP

created branch time in 8 days

push eventpspdev/binutils

Alan Modra

commit sha db543a7de3f3356133ef3f7f7fc9ae444fd55325

testsuite: Don't start directives in first column Fixes fails on hppa64-hp-hpux11.23 * testsuite/gas/elf/section25.s: Don't start directives in first column. * testsuite/gas/elf/section26.s: Likewise.

view details

Alan Modra

commit sha 5072b52d28f56586a708019a97b8a4456c0c7212

csky: fix annobin test fails * elf32-csky.c (is_mapping_symbol_name): New function. (csky_elf_is_target_special_symbol): Likewise. (csky_elf_maybe_function_sym): Likewise. (bfd_elf32_bfd_is_target_special_symbol): Define. (elf_backend_maybe_function_sym): Define.

view details

Alan Modra

commit sha 337d0bf887a3ed6b6b2123fecfec0736640edcaf

PR27755, powerpc-ld infinite loop PR 27755 * elf32-ppc.c (ppc_elf_inline_plt): Do increment rel in loop.

view details

Alan Modra

commit sha b293661219c36e72acb80502a86b51160bb88cfd

PPC: ensure_undef_dynamic on weak undef only in plt It's slightly weird to have a call to a weak function not protected by a test of that function being non-NULL, but the non-NULL test might be covered by a test of another function. For example: if (func1) { func1 (); func2 (); } where func2 is known to exist if func1 exists. * elf32-ppc.c (allocate_dynrelocs): Call ensure_undef_dynamic for weak undefined symols that only appear on PLT relocs. * elf64-ppc.c (allocate_dynrelocs): Likewise.

view details

Alan Modra

commit sha 4916030821bb0b052091bd1e29f1851e1512a056

PPC: undefweak dynamic relocs This makes the default for ppc to keep dynamic relocs on undefweak symbols when the code won't cause DT_TEXTREL (for instance when -fPIE or -fPIC). If ld is given -z dynamic-undefined-weak then dynamic relocations will be created for non-PIC at the expense of possibly causing DT_TEXTREL to be set on ppc32. Note that DT_TEXTREL and GNU indirect functions are incompatible. * elf32-ppc.c (allocate_dynrelocs): Keep dyn_relocs for undefweak symbols when -z dynamic-undefined-weak or when there are no dynamic relocs in read-only sections and -z nodynamic-undefined-weak is not given. * elf64-ppc.c (allocate_dynrelocs): Likewise.

view details

Andrew Burgess

commit sha d389a1a7692d247b6153fc6a98ebc43d7070fc2e

gdb/testsuite: update expected results in gdb.python/py-startup-opt.exp The test gdb.python/py-startup-opt.exp checks the behaviour of GDB's: set python dont-write-bytecode on This flag (when on) stops Python creating .pyc files. The test first checks that .pyc files will be created, then turns this option on and checks .pyc files will not be created. However, if the user has PYTHONDONTWRITEBYTECODE set in their environment then this will prevent Python from creating .pyc files, as such the first test, that .pyc files are being created, currently fails. We could unset PYTHONDONTWRITEBYTECODE, however, until Python 3.8 there is no way to control where Python writes the .pyc files. As the GDB developer clearly doesn't want .pyc files created in their file-system it feels wrong to silently unset this environment variable. My proposal then, is that we just spot when this environment variable is set and adjust the expected results. My hope is that across all GDB developers some will be running with PYTHONDONTWRITEBYTECODE unset, so this feature will be fully tested at least some of the time. gdb/testsuite/ChangeLog: PR testsuite/27788 * gdb.python/py-startup-opt.exp (test_python_settings): Change the expected results when environment variable PYTHONDONTWRITEBYTECODE is set.

view details

Jan Beulich

commit sha 4c398cc06d333fcb04772c04ea18db68587e8a1f

x86: don't request useless overflow checking Relocations with a bitsize matching the architecture's address width can't usefully use an overflow checking approach other than "dont" or "signed": All others involve perhaps complex calculations in _bfd_relocate_contents() (or, not as severe, in bfd_check_overflow()) without ever finding anything to complain about - because of the address width masking applied. Avoid this unnecessary overhead and switch all such reloc types to "dont". Note that "signed" checking with rela relocations (i.e. x86-64 here) is only going to be useful if the addend actually got passed to _bfd_relocate_contents() (and maybe others) instead of bogusly adding in prior section contents (which apparently is assumed to be zero, and hence again no overflow would ever be detected). See https://sourceware.org/pipermail/binutils/2021-April/116164.html.

view details

Jan Beulich

commit sha deea497309415b15c5fe5f5052bc7e529fe541c1

x86: fold both instances of lex_got() I see no reason at all for us to carry two copies of almost identical code. The differences, apart from the table entries, are benign. And the #ifdef-ary doesn't really get any worse.

view details

Jan Beulich

commit sha 3e301ce0b54002d92808f6bba08b8f793a5cdfa5

x86: use UNIX EOL in secrel testcase For some reason these were using Windows EOL.

view details

Jan Beulich

commit sha 5e0a033bd2927a027a5fb2c93d9e403c4f505bd0

x86: allow @secrel32 also in data definitions Now that lex_got() is uniform for all targets using it, permit COFF targets to also use @secrel32 with, in particular, .long. This is more natural than the custom .secrel32 directive, and also allows more flexibility (the "+six" form of the two added test lines doesn't work with a .secrel32 equivalent, in that it silently produces an unintended relocation type). As an extra benefit this also makes sure that data definitions in Intel syntax mode would get treated like they do for e.g. ELF targets.

view details

Simon Marchi

commit sha f08708cbf59ec153eac33d7a2a99ef99f1ca825a

sim: add ATTRIBUTE_PRINTF / ATTRIBUTE_NULL_PRINTF where necessary I finally got the all-targets sim building with Clang, these are all the instances where an ATTRIBUTE_PRINTF or ATTRIBUTE_NULL_PRINTF attribute needed to be added to avoid errors like: /home/simark/src/binutils-gdb/sim/aarch64/../common/sim-profile.c:464:19: error: format string is not a string literal [-Werror,-Wformat-nonliteral] vfprintf (fp, fmt, ap); ^~~ There are more fixes needed to get everything building, but adding these attributes is trivial enough, so I send them all in a single patch. Adding the format attributes introduces some format string errors when building with GCC (because now format strings are checked), so corresponding changes are needed to avoid breaking the build. Other than simple format string specified changes, there is this one: /home/simark/src/binutils-gdb/sim/aarch64/../common/hw-events.c: In function 'hw_event_queue_schedule': /home/simark/src/binutils-gdb/sim/aarch64/../common/hw-events.c:95:15: error: too many arguments for format [-Werror=format-extra-args] 95 | NULL, dummy); | ^~~~~ We can fix it and avoid using a dummy variable by simply calling hw_event_queue_schedule_tracef instead of hw_event_queue_schedule_vtracef. sim/arm/ChangeLog: * armdefs.h (ARMul_ConsolePrint): Use format attribute. * wrapper.c (op_printf): Likewise. sim/bfin/ChangeLog: * interp.c (sim_open): Adjust format string specifier. sim/common/ChangeLog: * hw-events.h (hw_event_queue_schedule_tracef): Use format attribute. (hw_event_queue_schedule_vtracef): Likewise. * hw-tree.h (hw_tree_vparse): Likewise. * sim-profile.c (profile_vprintf): Likewise. * sim-trace.c (dis_printf): Likewise. * sim-trace.h (trace_printf): Likewise. (trace_vprintf): Likewise. * sim-utils.h (sim_do_commandf): Likewise. * hw-events.c (hw_event_queue_schedule): Use hw_event_queue_schedule_tracef. sim/rx/ChangeLog: * trace.c (op_printf): Likewise. sim/v850/ChangeLog: * interp.c (sim_open): Adjust format string specifier. Change-Id: I1445115ce57db15bb8e35dca93014555e7555794

view details

Tom Tromey

commit sha 8228833924fa3c92a436a5f938a94dae180773f9

Fix x86_64 mingw build PR build/27807 points out that my recent changes to the Windows port missed a spot in win32-i386-low.cc -- a call to win32_Wow64GetThreadContext remained, causing link errors in gdbserver. This happened because I tested an i686 build, but this code is only used on an x86_64 build. This patch fixes the bug. I am checking it in. gdbserver/ChangeLog 2021-05-03 Tom Tromey <tromey@adacore.com> PR build/27807: * win32-i386-low.cc (i386_get_thread_context): Call Wow64GetThreadContext, not win32_Wow64GetThreadContext.

view details

Christoph Muellner

commit sha 6bdf164fc57e0191d40d903ab549666a12fc77a8

RISC-V: PR27764, Add tests for A extension gas/ PR 27764 * testsuite/gas/riscv/a-ext-64.d: New testcase. * testsuite/gas/riscv/a-ext-64.s: Likewise. * testsuite/gas/riscv/a-ext.d: Likewise. * testsuite/gas/riscv/a-ext.s: Likewise. Signed-off-by: Christoph Muellner <cmuellner@gcc.gnu.org>

view details

Jim Wilson

commit sha 7b06fcf5662c021dfd8a4f7b3b41c1be510adec3

RISC-V: PR27764, Add tests for A extension ChangeLog entry for last patch.

view details

GDB Administrator

commit sha ae0373ce077724b52ceab6e095cc6509a7eea48f

Automatic date update in version.in

view details

Tom de Vries

commit sha 225bda24db9671e2087fda892f94141625836a40

[gdb/guile] Don't allow libguile to change libgmp mem fns Since gdb commit 880ae75a2b7 "gdb delay guile initialization until gdbscm_finish_initialization" I'm running into: ... (gdb) print My_Var > 10.0^M free(): invalid pointer^M ERROR: GDB process no longer exists GDB process exited with wait status 5995 exp9 0 0 CHILDKILLED SIGABRT SIGABRT UNRESOLVED: gdb.ada/fixed_cmp.exp: gnat_encodings=all: print My_Var > 10.0 ... The problem is that both gdb and libguile try to set the libgmp memory functions, and since the gdb commit the ones from libguile are effective, which results in gdb freeing some memory in a way that is not compatible with the way that memory was actually allocated. The fact that libguile tries to set the libgmp memory functions is a bug which should be fixed starting version v3.0.6. Meanwhile, work around this in gdb by not allowing libguile to set the libgomp memory functions. Tested on x86_64-linux. gdb/ChangeLog: 2021-05-04 Tom de Vries <tdevries@suse.de> PR guile/27806 * guile/guile.c (gdbscm_initialize): Don't let guile change libgmp memory functions.

view details

Mike Frysinger

commit sha 5ee0bc23a68fe2a6a7717b31fda1db878b2c9764

sim: clean up bfd_vma printing A lot of this code predates the bfd_vma format define, so we have a random mix of casts to known types so we can printf the value. Use the BFD_VMA_FMT that now exists to simplify and reliability output across different build configs.

view details

Mike Frysinger

commit sha aa0fca163e1736e158fd3922cbbc31b85c9c7df7

sim: add support for build-time ar & ranlib This is needed when building for a target whose ar & ranlib are incompatible with the current build system. For example, building for Windows on a Linux system. Then manually import the automake rule for libigen.a, but tweak the tool variables to use the FOR_BUILD variants.

view details

Nick Clifton

commit sha a8d6316b67d52eaa1b7b311084ddff71a66f7cc0

Replace AC_PROG_CC with AC_PROG_CC_C99 in top level configure file. 2021-05-04 Nick Clifton <nickc@redhat.com> * configure.ac (AC_PROG_CC): Replace with AC_PROG_CC_C99. * configure: Regenerate.

view details

Nick Clifton

commit sha bd6d8601f304d03ecdebe1b1a7d48666845a91aa

Define bfd_realloc(ptr,0) to return allocated memory, whilst bfd_realloc_or_free(ptr,0) frees ptr. * libbfd.c (bfd_malloc): Provide some documenation. Treat a size of 0 as 1. (bfd_realloc): Likewise. (bfd_zmalloc): Likewise. (bfd_realloc_or_free): Provide some documentation. Treat a size of 0 as a request to free. * libbfd-in.h (bfd_realloc): Remove prototype. (bfd_realloc_or_free): Remove prototype. (bfd_zmalloc): Remove prototype. * libbfd.h: Regenerate.

view details

push time in 8 days

create barnchpspdev/binutils

branch : binutils-2_23_2

created branch time in 8 days

create barnchpspdev/binutils

branch : binutils-2_23_2-PSP

created branch time in 8 days

issue commentPSP-Archive/dosbox_psp

SDL or not?

@pierrelouys explain yourself :laughing: image

Ringdingcoder

comment created time in 9 days

issue commentPSP-Archive/dosbox_psp

SDL or not?

Hm, yeah, it looks like it linked without it so perhaps it should be removed from the config.

Ringdingcoder

comment created time in 9 days

issue commentpspdev/newlib

Missing snprintf and vsnprintf

Apparently @fjtruji is on the case.

glebm

comment created time in 11 days

startedhistoricalsource/narc

started time in 19 days

pull request commentatsamd-rs/atsamd

Add methods for the USB Start Of Frame interrupt

Me neither tbh. @twitchyliquid64 ?

ianrrees

comment created time in a month

pull request commentatsamd-rs/atsamd

Update metro_m0 BSP and examples

Thanks, the Metro M0 is the oldest BSP I think. Fine with dropping rando.

ianrrees

comment created time in a month

pull request commentatsamd-rs/atsamd

Moved unproven feature gates to trait impl blocks

@sajattack, what do you think about making unproven unconditional for the time being? Seems more trouble than it's worth

Yeah go for it.

Sympatron

comment created time in a month

pull request commentatsamd-rs/atsamd

Embedded graphics 7.0 update

@jessebraham @twitchyliquid64 Do either of you want to try wio terminal before I merge this?

jacobrosenthal

comment created time in a month

pull request commentatsamd-rs/atsamd

Emebedded graphics 7.0 update

Looks like rustfmt hates your doc comment or something?

jacobrosenthal

comment created time in a month

push eventatsamd-rs/atsamd

Ian Rees

commit sha 8c4035668064609ff1561e32e17e92165cb70187

Add `pub use nb;` to HAL prelude

view details

push time in a month

PR merged atsamd-rs/atsamd

Add `pub use nb;` to HAL prelude

Just a little thing - this means that crates depending on the HAL don't need to explicitly depend on nb to handle the nb::Results and such returned by HAL methods.

+2 -0

0 comment

1 changed file

ianrrees

pr closed time in a month

Pull request review commentatsamd-rs/atsamd

Emebedded graphics 7.0 update

+[default.probe]

Sorry, I didn't click the right spot evidently.

jacobrosenthal

comment created time in a month

PullRequestReviewEvent
PullRequestReviewEvent

push eventatsamd-rs/atsamd

Bradley Harden

commit sha 854e3e1dc271c307e3d2ff983e6c2463fe7ac2cc

Remove the sercom::v2::Pad type (#451) The `sercom::v2::Pad` type was a simple wrapper around a `gpio::v2::Pin` type. Its purpose was to ensure that each `Pin` was properly configured to act as the corresponding SERCOM `Pad`. However, one of my goals in designing the `v2::spi` API was to avoid the need for users to manually convert `Pin` types to `Pad` types. As that module progressed, it became clear that the `v2::Pad` type served no real purpose. All the same constraints could be imposed using a slightly different approach to type-level programming. Remove the `v2::Pad` type and modify the `sercom::v2::pad` module accordingly. Update the `v1::Pad` type as well. Rename some of the type-level items in the `v2::pad` module and improve the documentation. Update the `sercom::v1` peripheral APIs to accept both `v1::Pad` types and the equivalent of a `v2::Pad`, which is simply a properly configured `v2::Pin`. Finally, redefine the type parameters of `v2::spi::Pads` to be `OptionalPad`s rather than `OptionalPinId`s, and provide a new `PadsFromIds` to make up for it. This change increases consistency in the definition of the `spi::Pads` type, and it allows me to remove a significant amount of trait boilerplate needed to make it all work.

view details

push time in a month

PR merged atsamd-rs/atsamd

Remove the sercom::v2::Pad type and redefine the v2::spi::Pads type

The sercom::v2::Pad type was a simple wrapper around a gpio::v2::Pin type. Its purpose was to ensure that each Pin was properly configured to act as the corresponding SERCOM Pad. However, one of my goals in designing the v2::spi API was to avoid the need for users to manually convert Pin types to Pad types. As that module progressed, it became clear that the v2::Pad type served no real purpose. All the same constraints could be imposed using a slightly different approach to type-level programming.

Remove the v2::Pad type and modify the sercom::v2::pad module accordingly. Update the v1::Pad type as well. Rename some of the type-level items in the v2::pad module and improve the documentation. Update the sercom::v1 peripheral APIs to accept both v1::Pad types and the equivalent of a v2::Pad, which is simply a properly configured v2::Pin.

Finally, redefine the type parameters of v2::spi::Pads to be OptionalPads rather than OptionalPinIds, and provide a new PadsFromIds to make up for it. This change increases consistency in the definition of the spi::Pads type, and it allows me to remove a significant amount of trait boilerplate needed to make it all work.

+1585 -2035

6 comments

19 changed files

bradleyharden

pr closed time in a month

issue commentatsamd-rs/atsamd

v0.13 Roadmap

Should we include #450 as well?

jbeaurivage

comment created time in a month

pull request commentatsamd-rs/atsamd

Remove the sercom::v2::Pad type and redefine the v2::spi::Pads type

@bradleyharden would you like to wait for comments from the people you've asked to take a look, or should I look it over / merge?

bradleyharden

comment created time in a month

issue closedsajattack/st7735-lcd-rs

Make set_address_window public

Hey, how do I use methods like write_pixels if I cant actually set the drawing window myself? The method responsible for settings that window seems to be set_address_window, which isnt pub.

What I'm trying to do is draw to the screen line by line, without setting the window to that line every time. Basically, set the window to the whole screen, draw a line, compute some stuff, draw the next line, etc.

closed time in a month

netthier

push eventsajattack/st7735-lcd-rs

nett_hier

commit sha 82690cb943c413602f5542874fb5c6fa7328959f

Make set_address_window a public method

view details

nett_hier

commit sha 43e00bcee01db25082a50b2a36559c99fa5c95a4

Bump crate version

view details

push time in a month

PR merged sajattack/st7735-lcd-rs

Make set_address_window a public method

See issue #16

+2 -2

0 comment

2 changed files

netthier

pr closed time in a month

PR closed atsamd-rs/atsamd

Arduino Nano 33 IOT WiFi NINA SPI Master
+34 -2

5 comments

1 changed file

olback

pr closed time in a month