> Note that for copyright purposes a series of unrelated small changes
> counts as a big change. If you truly can't do the paperwork, then
> it's probably best for the project if you avoid sending actual
> patches. Sorry about that.
A series of *related* small changes certainly would count as a
Jay K writes:
> Understood, but I'll have to stick to "small" changes as I can't get the
> papers.
Note that for copyright purposes a series of unrelated small changes
counts as a big change. If you truly can't do the paperwork, then
it's probably best for the project if you avoid sending actu
work for Darwin
targets?.
What, people use -masm=intel and masm/nasm/yasm instead of gas? Or just to
human read the output?
Thanks,
- Jay
--------------------
> From: ebotca...@adacore.com
> To: jay.kr...@cornell.edu
> Subject: Re: rep prefix doesn't work with
> Proposed patch below/attached.
> (-w to hide indent change)
See http://gcc.gnu.org/contribute.html for guidelines.
> I'll open a bug.
See http://gcc.gnu.org/bugs for guidelines.
Generally speaking, posting a patch inlined in a message on gcc@gcc.gnu.org
will most likely result in it being
