From Fedora Project Wiki

m (→‎GCC work: Reverse order, to most-recent first)
(→‎GCC work: Add link to blog post about my GCC 10 static analysis work)
Line 14: Line 14:


= GCC work =
= GCC work =
* GCC 10:
** Blog post: [https://developers.redhat.com/blog/2020/03/26/static-analysis-in-gcc-10/ Static analysis in GCC 10]
* GCC 9:
* GCC 9:
** Blog post: [https://developers.redhat.com/blog/2019/03/08/usability-improvements-in-gcc-9/ Usability improvements in GCC 9]  
** Blog post: [https://developers.redhat.com/blog/2019/03/08/usability-improvements-in-gcc-9/ Usability improvements in GCC 9]  

Revision as of 11:39, 21 April 2020

David Malcolm

Email: dmalcolm@redhat.com

My Fedora People page: http://dmalcolm.fedorapeople.org/

My blog: http://dmalcolm.livejournal.com/

A very old, out-of-date Red Hat People Page: http://people.redhat.com/dmalcolm

I'm currently working on GCC upstream. Previously I worked on the Python runtimes within Fedora and Red Hat Enterprise Linux.

I'm interested in static code analysis

GCC work

Some of the software I've written

  • libgccjit: a branch of GCC allowing it to be built as a shared library for use in Just-In-Time compilation
  • gcc-python-plugin: allowing you to write new GCC plugins in Python.
  • cpychecker: a static analysis pass for GCC to find bugs in C extensions to Python, written in Python using gcc-python-plugin
  • gdb Python hooks for debugging CPython itself
  • gdb-heap, an extension to gdb for analyzing malloc/free
  • squeal: a SQL-like syntax for use in shell pipelines
  • asmdiff: tool for comparing objdump results
  • gccinvocation: Python module for parsing GCC invocation lines
  • jamais-vu: a tool for working with DejaGnu output
  • firehose: a proposed common format for static analyzer output, along with a Python module for working with it
  • mock-with-analysis: a way of rebuilding an RPM in mock, injecting static analysis, and capturing the result in Firehose format
  • gcc-build: some scripts to make it easier to hack on GCC

Older stuff