Woong Jun

Making a package for Debian distros is in progress and it needs a list of standard headers from `gcc` that should be included in it.

Given an lvalue as an operand of the unary `+`, lcc generates an lvalue even if it should not. Thus, ``` void foo(void) { int x, *p; p = &+x;...

Trying to assign a struct to a unsigned bitfield triggers an assertion failure. For example, given this: ``` void f(void) { struct { int foo:3; } x; struct { unsigned...

lcc currently fails to correctly handle composite types in conditoinal expressions. For example, ``` void foo(void) { extern int cond; int (*a)[], (*b)[10], (*c)[20]; c = cond? a: b; c...

This commit lets lcc correctly diagnose the following code: ``` typedef void (*fp_t)(void); fp_t func(fp_t param) { return (void *)0; /* line A */ } int main(void) { fp_t t...

Some candidates include (but not limited to) - recently added - 1970's, 1980's and so on

Allow these actions within task functions: - getting remaining time to next run and - changing schedules

Allowing different types of schedules in a single specification is useful, for example, when `single: true`.

Completion callback invoked twice

1

The issue #122 I reported before seemed to be fixed by fdb1b5d7d9802143d26fc92a3292fba3cdbc961f, but that fix introduced another issue. The latest release invokes the completion callback twice for [this file](https://github.com/leetreveil/musicmetadata/files/836403/twice.zip). ```...