梅花鹿吃什么| sos代表什么| 为什么睡不醒| 两面派是什么意思| 跑步的配速是什么意思| 宫颈纳氏囊肿是什么意思| 雄激素是什么意思| 腊月初六是什么星座| co是什么| 五行金代表什么| 孩子咬嘴唇是什么原因| 下午五点半是什么时辰| 喉结肿大是什么原因| 头出汗多至头发湿透是什么原因| 头疼发烧是什么原因| 风景旧曾谙是什么意思| 舌头臭是什么原因| 湄公鱼是什么鱼| 晚上七点半是什么时辰| 什么叫牙周炎| 生化妊娠什么意思| 息肉和痔疮有什么区别| 生日送百合花代表什么| 女人胃寒吃什么好得快| 顺子是什么意思| 血脂高是什么原因引起| 4月8号什么星座| 航班是什么意思| 牙痛吃什么好| 什么是碳水化合物食物| 梦见滑雪是什么意思| 女性阴毛变白是什么原因| 扁桃体炎吃什么消炎药| 小孩干咳是什么原因| 儿童风寒咳嗽吃什么药| 爱是什么词| 儿童发烧挂什么科| 回南天是什么时候| feel什么意思| 长寿的秘诀是什么| 脑管瘤的症状是什么| 和女生聊什么话题| 睡觉脚抽筋是什么原因引起的| 为什么叫新四军| 迅雷不及掩耳之势是什么意思| 画蛇添足的寓意是什么| 什么中药补气血效果最好| 老夫是什么意思| 证明是什么意思| 鬼怕什么东西| 血压低压高吃什么药| 孕妇腿抽筋是什么原因| 河南有什么市| 旦辞爷娘去的旦是什么意思| 角弓反张是什么意思| mrmrs是什么牌子| 小鱼爱吃什么| 6月12号是什么星座| 什么叫扁平疣| classic是什么意思| 赵本山什么学历| 处女座男和什么星座最配| 上海的市花是什么| 鸡是什么意思| 翡翠是什么玉| 无创dna是检查什么的| 21三体高风险是什么原因造成的| 四十属什么| 不敢造次是什么意思| 法本是什么意思| 颜值担当是什么意思| 芒果有什么好处和坏处| 80年属什么| 妈祖叫什么名字| 226是什么意思| 吃什么药能来月经| 胃癌挂什么科| 30周做什么检查| 阴囊潮湿吃什么食物| 促销员是做什么的| 气胸有什么症状| 欧根纱是什么面料| 局部癌变是什么意思| 肋骨神经痛吃什么药| 肺实性结节是什么意思| 下午一点到三点是什么时辰| 眼皮一直跳是什么原因| 下颌关节紊乱挂什么科| 地球属于什么星系| 芒果不能和什么食物一起吃| 梦见卖东西是什么意思| 接触性皮炎用什么药| 姜太公钓鱼愿者上钩是什么意思| 狗狗流鼻涕吃什么药| 银耳长在什么地方| zoe什么意思| 蛔虫长什么样| 老花眼是什么症状| 乙肝表面抗体弱阳性什么意思| 什么是醪糟| 手抖吃什么药最好| 世界上最深的湖是什么| 吃什么排铅效果最好| 丝绦是什么意思| 香港奶粉为什么限购| 银饰为什么会变黑| pt是什么材质| mect是什么意思| 很man是什么意思| 气垫是什么| 吃什么补维生素D效果最好| 祖师香是什么意思| roa是什么| 有色眼镜是什么意思| trans什么意思| 血清铁蛋白是检查什么| 锡字五行属什么| 腺肌症不治疗会导致什么结果| 坎坷人生是什么生肖| 白头发多是什么原因| 为什么会有霉菌性阴道炎| 一个入一个肉念什么| 用苦良心是什么意思| 结婚27年是什么婚| 指甲有横纹是什么原因| 糖尿病人能吃什么| 美妞是什么意思| 精尽人亡什么意思| 九月十二号是什么星座| 梦见鸡是什么意思| m2是什么单位| 肾功能不好吃什么药调理| 一马平川什么意思| 心率低有什么危害| 小孩贫血有什么症状| 什么的童话| 脑梗输什么液效果最好| 不想吃饭是什么原因| 胎儿双顶径是什么意思| 平权是什么意思| 生产周期是什么意思| 威士忌属于什么酒| 罗布麻是什么东西| 芹菜炒什么| 血糖高的人早餐吃什么好| 心脏跳的慢吃什么好| 额头冒痘是什么原因| 做梦梦到牙齿掉了是什么意思| 抗衡是什么意思| 子宫内膜脱落是什么意思| 胃炎伴糜烂是什么意思| 努尔哈赤是什么民族| 进去是什么感觉| 生完孩子可以吃什么水果| 糟卤可以做什么菜| gr是什么单位| 貌合神离是什么意思| 风团是什么原因引起的| 女性尿酸低是什么原因| 医院规培生是什么意思| 没有排卵是什么原因| 1970年属什么生肖| 可甜可盐什么意思| 蓝色加什么颜色是紫色| 女人阳虚吃什么药效果最好| 舌苔厚白应该吃什么| 避孕套上的油是什么油| 察言观色是什么意思| 眼睛红血丝是什么原因| 意欲何为是什么意思| 29周岁属什么生肖| 手掌发红是什么原因| 外周血是什么意思| 118号是什么星座| 健康管理是什么专业| 吃李子有什么好处| 司马懿字什么| 4月20是什么星座| 搪塞是什么意思| 气色是什么意思| 三土念什么| 子宫复旧是什么意思| 有且仅有什么意思| 小孩睡觉趴着睡是什么原因| 黄痰吃什么药最好| 静夜思是什么季节| 斛什么意思| 诺如病毒拉的大便是什么样的| 什么人容易得骨髓瘤| 什么是频率| 手指甲有黑色条纹是什么原因| 阵雨是什么意思| 707是什么意思| 脑垂体挂什么科| 子宫肌瘤是什么病| 鞋底md是什么材质| 什么是山海经| 双日是什么意思| 长期喝豆浆有什么好处和坏处| 菊花像什么比喻句| 纠察是什么意思| 2018年属什么| 转氨酶偏高是什么原因| 胆黄素高是怎么回事有什么危害| 三言两语是什么生肖| 荨麻疹可以吃什么水果| 落子是什么意思| 什么样的人容易得脑瘤| 更年期出虚汗吃什么药| 梦见好多羊是什么意思| 手指尖发麻是什么原因| 补蛋白吃什么最好| 桂林山水甲天下是什么意思| bug什么意思| 夹生饭是什么意思| 亦的意思是什么| 金黄色葡萄球菌是什么| 牙龈出血什么原因| 喝水多尿多是什么原因| 拼音b像什么| 梦见自己死了又活了是什么意思| 1974属什么生肖| 梦见喝水是什么意思| 肌酐高吃什么药好| 刮目相看是什么意思| 咲是什么意思| 最好的红酒是什么牌子| 前列腺钙化是什么病| 神经系统是由什么组成的| 乌鸡白凤丸有什么功效| 偶发室上性早搏是什么意思| 中国什么时候打仗| 甘草有什么功效| 上嘴角有痣代表什么| 吃什么水果对皮肤好又美白| 嗓子痒是什么原因| 光棍一条是什么生肖| 铁公鸡是什么意思| 功能性子宫出血是什么原因造成的| 哈西奈德溶液治什么病| 专升本需要考什么| 芒果吃了有什么好处| 尿蛋白高有什么危害| wedding什么意思| 甲胎蛋白是什么意思| 史莱姆是什么意思| eu是什么元素| 大便呈绿色是什么原因| 什么样的脸型有福| 生生不息是什么意思| 鸡血藤有什么作用| 治疗呼吸道感染用什么药最好| 水痘长什么样| 腹膜炎吃什么药| 基尼是什么货币| 为什么会早产| 骨科什么意思| 佛法无边是什么意思| 不让看朋友圈显示什么| 黄体破裂是什么意思| 小青蛙吃什么| 常染色体是什么| 气血不足什么症状| 甲沟炎用什么药膏| 百度

IMF上调中国今明两年经济增长预期至6.6%和6.2%

百度   亲,昨天晚上睡好了吗?  早上眼霜、遮瑕液还够用吗?  黑眼圈能遮住吗?  大脑今天还正常运转吗?  ……  3月21日,我们迎来第18个“世界睡眠日”,今年睡眠日的主题为“规律作息,健康睡眠”,这八个字看似简单却很难做到,随着社会节奏加快,已经有越来越多的人加入睡不够、睡不好、不肯睡的“特困生”队伍了,这都是为什么呢?  是谁偷走了“我”的睡眠?  据《2018中国互联网网民睡眠白皮书》,近九成网友习惯在睡前玩手机,平均时间为65分钟,58%的95后睡前玩手机平均时间达到80分钟。

We strongly encourage contributions in the form of features, new or improved optimizations, bug fixes, documentation updates, web page improvements, etc....

If you're new to GCC, please also see the Getting Started section of the GCC Wiki.

There are certain legal requirements and style issues which contributions must meet:


Before we can incorporate significant contributions, certain legal requirements must be met.

The FSF prefers that a contributor files a copyright assignment for large contributions. See some documentation by the FSF for details and contact us (either via the gcc@gcc.gnu.org list or the GCC maintainer that is taking care of your contributions) to obtain the relevant forms. The most common forms are an assignment for a specific change, an assignment for all future changes, and an employer disclaimer, if an employer or school owns work created by the developer. It's a good idea to send assign@gnu.org a copy of your request.

Alternatively, a contributor can certify the Developer Certificate of Origin for their contribution by adding the Signed-off-by: tag to their submission. Contributors with commit access can certify the DCO for all future commits by adding their name to the DCO list in the MAINTAINERS file.

We can accept small changes without copyright assignment or DCO certification.

Coding Standards

All contributions must conform to the GNU Coding Standards. There are also some additional coding conventions for GCC; these include documentation and testsuite requirements as well as requirements on code formatting.

Submissions which do not conform to the standards will be returned with a request to address any such problems. To help with the preparation of patches you can use the script contrib/check_GNU_style.sh.

Testing Patches

All patches must be thoroughly tested. We encourage you to test changes with as many host and target combinations as is practical. In addition to using real hardware, you can use simulators.

Much of GCC's code is used only by some targets, or used in quite different ways by different targets. When choosing targets to test a patch with, make sure that your selections exercise all aspects of the code you are changing.

You will of course have tested that your change does what you expected it to do: fix a bug, improve an optimization, add a new feature. Where possible you should automate these tests and add them to GCC's testsuite. You must also perform regression tests to ensure that your patch does not break anything else. Typically, this means comparing post-patch test results to pre-patch results by testing twice or comparing with recent posts to the gcc-testresults list.

Which tests to perform

If your change is to code that is not in a front end, or is to the C or C++ front ends, you must perform a complete build of GCC and the runtime libraries included with it, on at least one target. You must bootstrap all default languages, not just C and C++, and run all testsuites. For a normal native configuration, running

make bootstrap
make -k check

from the top level of the GCC build tree (not the gcc subdirectory) will accomplish this.

If your change is to the C++ front end, you need to run the C++ testsuite in all standard conformance levels. For a normal native configuration, running

make -C gcc -k check-c++-all

from the top level of the GCC build tree will accomplish this.

If your change is to a front end other than the C or C++ front end, or a runtime library other than libgcc, you need to verify only that the runtime library for that language still builds and the tests for that language have not regressed. (Most languages have tests stored both in the gcc subdirectory, and in the directory for the runtime library.) You need not bootstrap, or test other languages, since there is no way you could have affected them.

Since the Ada front end is written in Ada, if you change it you must perform a complete bootstrap; however, running other language testsuites is not necessary.

In all cases you must test exactly the change that you intend to submit. The tree where you perform this test should not have any other changes applied.

Documentation Changes

Documentation changes do not require a new bootstrap (a working bootstrap is necessary to get the build environment correct), but you must perform make info and make dvi and correct any errors. You should investigate complaints about overfull or underfull hboxes from make dvi, as these can be the only indication of serious markup problems, but do not feel obliged to eliminate them all.

Web Site Changes

Changes to the web site must validate as HTML 5. To validate your changes, use the "upload file" mode of the validator.

Please mark patches with the tag [wwwdocs] in the subject line.

More about our web pages.

Submitting Patches

Every patch must have several pieces of information, before we can properly evaluate it:

A description of the problem/bug and how your patch addresses it.
For new features a description of the feature and your implementation. For bugs a description of what was wrong with the existing code, and a reference to any previous bug report (in the GCC bug tracker) and any existing testcases for the problem in the GCC testsuite.
Testcases
If you cannot follow the recommendations of the GCC coding conventions about testcases, you should include a justification for why adequate testcases cannot be added.
ChangeLog
A ChangeLog entry as plaintext; see the GCC coding conventions and GNU Coding Standards for further information.
The git gcc-commit-mklog command from gcc-git-customization.sh (see here) automates a lot of ChangeLog generation.
Bootstrapping and testing
State the host and target combinations you used to do proper testing as described above, and the results of your testing.
The patch itself
The patch should include everything you are changing (including regenerated files which should be noted in the ChangeLog e.g. "* configure: Regenerate.").

Don't mix together changes made for different reasons. Send them individually. Ideally, each change you send should be impossible to subdivide into parts that we might want to consider separately, because each of its parts gets its motivation from the other parts. In particular, changes to code formatting to conform to coding standards are best not mixed with substantive changes, because that makes it difficult to see what the real changes are. (In the case of a very large reorganization of code, it may make sense to separate changes even further to make it clearer what has changed; for example, by first sending structural changes that make subsequent changes easier but do not change GCC's behavior, then new code, then the changes that actually make use of the new code and change GCC's behavior.)

We prefer patches posted as plain text or as MIME parts of type text/x-patch or text/plain. It is strongly discouraged to post patches as MIME parts of type application/whatever, disposition attachment or encoded as base64 or quoted-printable.

If the patch is too big or too mechanical, posting it gzipped or bzip2ed and uuencoded or encoded as a base64 MIME part is acceptable, as long as the ChangeLog is still posted as plain text.

When you have all these pieces, bundle them up in a mail message and send it to the appropriate mailing list(s). (Patches will go to one or more lists depending on what you are changing.) For further information on our source repository, see the Anonymous read-only Git access and Read-write Git access pages.

Many mail clients break patches pasted into the message body, primarily by wrapping long lines. See the Linux kernel documentation for ways to work around this.

(Everything listed here still applies if you can check in the patch without further approval under the GCC write access policies, except that diffs representing new files may be omitted, especially if large, since they can be accessed directly from the repository.)

E-mail subject lines

Your contribution e-mail subject line will become the first line of the commit message for your patch.

A high-quality e-mail subject line for a contribution contains the following elements:

The entire line (excluding the classifier) should not exceed 75 characters.

Classifier

The classifier identifies the type of contribution, for example a patch, an RFC (request for comments) or a committed patch (where approval is not necessary). The classifier should be written in upper case and surrounded with square brackets. This is the only component of the e-mail subject line that will not appear in the commit itself. The classifier may optionally contain a version number (vN) and a series marker (N/M). Examples are:

Component tags

A component tag is a short identifier that identifies the part of the compiler being modified. This highlights to the relevant maintainers that the patch may need their attention. Multiple components may be listed if necessary. Each component tag should be followed by a colon. For example,

Some large components may be subdivided into sub-components. If the subcomponent name is not distinct in its own right, you can use the form component/sub-component:.

Series identifier

The series identifier is optional and is only relevant if a number of patches are needed in order to effect an overall change. It should be a short string that identifies the series (it is common to all patches) and should be followed by a single dash surrounded by white space.

A Very Brief summary

The brief summary encapsulates in a few words the intent of the change. For example: cleanup check_field_decls. Although, very short, the summary should be distinct so that it will not be confused with other patches.

Bug number

If your patch relates a bug in the compiler for which there is an existing PR number the bug number should be stated. Use the short-form variant [PRnnnnn] without the Bugzilla component identifier and with no space between 'PR' and the number. The body of the commit message should still contain the full form (PR <component>/nnnnn) within the body of the commit message so that Bugzilla will correctly notice the commit. If your patch relates to two bugs, then write [PRnnnnn, PRmmmmm]. For multiple bugs, just cite the most relevant one in the summary and use an ellipsis instead of the second, or subsequent PR numbers; list all the related PRs in the body of the commit message in the normal way.

It is not necessary to cite bugs that are closed as duplicates of another unless there is something specific to that report that is not covered by the parent bug.

Other messages

Some large patch sets benefit from an introductory e-mail that provides more context for the patch series and describes how the patches have been broken up to provide for review. The convention is that such messages should follow the same format as described above, but the patch number should be set to zero, for example: [PATCH 0/7]. Remember that the introductory message will not be committed with the patches themselves, so it should not contain any important information that is not also covered in the individual patches. If you send a summary e-mail with a series it is a good idea to send the patches as follow-ups (essentially replies) to your initial message so that mail software can group the messages together.

If you submit a new version of a patch series, then you should start a new email thread (don't reply to the original patch series). This avoids email threads becoming confused between discussions of the first and subsequent revisions of the patch set. Your cover letter (0/nnn) should explain clearly what has been changed between the two patch series. Also state if some of the patches are unchanged between revisions; this saves maintainers having to re-review the patches they might have already reviewed in an earlier version. The individual patch messages should be as you expect them to be committed. It is a good idea to send a final follow-up message to the original thread indicating that a new version has been submitted.

Examples

Here are some complete examples, based on real commits to GCC.

git format-patch/send-email

The git format-patch tool generates an email in the desired format, with the commit subject line as the email subject line with [PATCH] prepended. You can send the resulting file as an email by itself (perhaps with git send-email) or as an attachment to another email.

Pinging patches, Getting patches applied

If you do not receive a response to a patch that you have submitted within two weeks or so, it may be a good idea to chase it by sending a follow-up e-mail to the same list(s). Patches can occasionally fall through the cracks. Please be sure to include a brief summary of the patch and the URL of the entry in the mailing list archive of the original submission.

If you do not have write access and a patch of yours has been approved, but not committed, please advise the approver of that fact. You may want to point out lack of write access in your initial submission, too.

Announcing Changes (to our Users)

Everything that requires a user to edit their Makefiles or source code is a good candidate for being mentioned in the release notes.

Larger accomplishments, either as part of a specific project, or long term commitment, merit mention on the front page. Examples include projects like tree-ssa, new back ends, major advances in optimization or standards compliance.

The gcc-announce mailing list serves to announce new releases and changes like front ends or back ends being dropped.

现在小麦什么价格 屠苏是什么意思 小孩子肚子疼吃什么药 老婆子是什么意思 荨麻疹吃什么药好
268数字代表什么意思 儿童流鼻涕吃什么药 婴儿黄疸母亲忌口什么 杨梅什么时候上市 张信哲为什么不结婚
物流是什么 乏是什么单位 排骨和什么菜搭配最好 什么样的秋天 猫牙米是什么米
盐酸舍曲林片治疗什么程度的抑郁 诸行无常是什么意思 积食发烧吃什么药 明朝北京叫什么 哈伦裤配什么鞋子好看
皮瓣手术是什么意思hcv8jop6ns4r.cn 上升星座代表什么hcv8jop5ns2r.cn 豆浆什么时候喝最好hcv8jop6ns3r.cn 肝内低密度灶是什么意思hkuteam.com 蝙蝠粪便是什么中药hcv7jop9ns9r.cn
哂是什么意思hcv8jop8ns7r.cn 7月25日是什么星座wmyky.com 颈椎曲度变直有什么症状hcv7jop5ns0r.cn 性功能障碍吃什么药hcv8jop5ns3r.cn iwc手表是什么档次hcv7jop9ns4r.cn
什么是情感障碍hcv8jop4ns5r.cn 羡煞旁人是什么意思hcv8jop9ns1r.cn 微信是什么时候开始有的hcv8jop6ns9r.cn 大便秘结是什么原因aiwuzhiyu.com 判处死刑缓期二年执行是什么意思hcv8jop0ns4r.cn
看痘痘挂什么科hcv8jop0ns4r.cn 维生素b族适合什么人吃dajiketang.com 措施是什么意思adwl56.com 肾绞痛可能由于什么原因引起hcv9jop0ns9r.cn 甚微是什么意思bysq.com
百度